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

[bwellsnc]

Ok, I built spicec using rpmbuild.  I copied the required mingw32 files over
 to my windows 7 machine.  It then would crash constantly.  I have no errors
on the server.  I then tried the linux client and it didn't have errors
either, but I do see these in the qemu output:

reds_show_new_channel: channel 1:0, connected successfully, over Non Secure
link


Also, the windows client is not going past:

watch_add: watch 0x16a4170, fd 20
watch_remove: watch 0x16a4170

Must be a DLL that I am missing or there is something that is being built
that windows doesn't need.




On Thu, Aug 5, 2010 at 3:21 AM, Gerd Hoffmann <kraxel at redhat.com> wrote:

> On 08/05/10 04:16, bwellsnc wrote:
>
>> I tried using mingw32-configure in the spice-0.5.2 directory and I get
>> this error:
>>
>> checking for PROTOCOL... configure: error: Package requirements
>> (spice-protocol) were not met:
>>
>> I have the spice-protocol package installed along with the
>> mingw32-spice-protocol.  If I run just a standard ./configure, I don't
>> get this error but I cannot build for win32 using this either.  I think
>> ming will build it, just need to be pointed in the direction on what
>> environmental variables need to be set.
>>
>
> From mingw32-spice.spec:
>
> # workaround: i686-pc-mingw32-pkg-config doesn't check
> $prefix/share/pkgconfig
> export
> PKG_CONFIG_PATH="%{_mingw32_datadir}/pkgconfig:%{_mingw32_libdir}/pkgconfig"
> export PROTOCOL_CFLAGS="$(pkg-config --cflags spice-protocol)"
> export PROTOCOL_LIBS="$(pkg-config --libs spice-protocol)"
>
> The source rpm also has a patch which will save you some work.
> If you manage to get a working spicec.exe send patches to the list please.
>
> thanks,
>  Gerd
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/spice-devel/attachments/20100805/7ac74c91/attachment.html>