[Spice-devel] Build Win 32 client for kraxel.fedorapeople.org

[bwellsnc]

With the version that I build using Visual Studio C++ Express, I now have a
gui where I can enter the server name, port number, secure port number, and
password.  This leads me to believe that mingw32 is not building all the
dependencies for spicec.exe.   I think the gui portion is being skipped for
some reason.  Also, I noticed that during the mingw32 rpm build the redc.rc
file is touched.  That is where I changed the below windows.h section.  I am
not sure if this has anything todo with anything either.


On Sat, Aug 7, 2010 at 4:18 PM, bwellsnc <bwellsnc at gmail.com> wrote:

> Ok, I was able to build it using Visual Studio C++ Express 2008. Here is
> how I did it:
> 1. Install Visual Studio C++ express 2008
> 2. Install python27 for windows and pyparsing parser for windows
> 3. Add the version of python to your PATH settings in windows.
> 4. Download spice, spice-protocol, and the unstable libs
> 5. extract these into a directory, they can be separate
> 6. Open the spice Visual Studio solution in visual studio C++
> 7. Right click on redc and select properties
> 8. Click the first general, and click the drop down by "Output Directory"
> and select Inherit from Parent, do the same for Intermediate Directory
> 9. Under the C/C++ selection, change the "Additional Include Directories",
> I placed mine in c:\spice_project, and my file entry looked like this:
>
> .;..;"C:\Spice_Project\spice-0.5.3\common";"C:\Spice_Project\spice-protocol";"C:\Spice_Project\spice-0.5.3\common\win";"C:\Spice_Project\spice-0.5.3\common\win\my_getopt-1.5";"C:\Spice_Project\spice-libs\include";"C:\Spice_Project\spice-libs\include\pixman-1";"C:\Spice_Project\spice-libs\include\CEGUI-0.6.2"
> 10. Under Linker, change the "Additional Library Directories" to point to
> the unstable library location.  My line looked like this:
> "C:\Spice_Project\spice-libs\lib"
> 11. After I did these changes, I right clicked on "Solution redc" and
> clicked clean solution, then rebuild solution.
> 12. There will be a complaint about afxres.h, change this to windows.h
> 13. Click re-build solution, there will be some complaints about vc100.pdb,
> but these can be ignored.
>
> If everything ran like mine, you should have a new directory under the
> spice client section called Debug.  There will be a spicec.exe under that
> directory.  You will now have to copy several .dll files from mingw32 to
> where ever you copy the spicec.exe file to.  Here is the list of files that
> are in my C:\SpiceClient Directory:
> avcodec-51.dll
> avcodec-51.lib
> avutil-49.dll
> avutil-49.lib
> CEGUI.log
> libcelt_0_5_1.dll
> libcelt_0_5_1D.dll
> libcrypto-10.dll
> libgcc_s_sjlj-1.dll
> libjpeg-7.dll
> libpixman-1-0.dll
> libqcairo-2.dll
> libssl-10.dll
> pthreadGC2.dll
> spicec.exe
> zlib1.dll
>
> You will notice a libcelt_0_5_1 and libcelt_0_5_1D, the one with the D is
> for the Debug version, and when you try to build a Release version, you will
> need a file without D.  If you need any help, just send me a quick not back.
>  I would really like this built in mingw32, but for now this works.
>
> Brent
>
> On Thu, Aug 5, 2010 at 12:06 PM, Gerd Hoffmann <kraxel at redhat.com> wrote:
>
>> On 08/05/10 15:54, bwellsnc wrote:
>>
>>> Ok, I built spicec using rpmbuild.  I copied the required mingw32 files
>>> over  to my windows 7 machine.  It then would crash constantly.
>>>
>>
>> Same failure I see, it (almost) instantly crashes.
>>
>> cheers,
>>  Gerd
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/spice-devel/attachments/20100808/bf1c8aef/attachment.html>