Hello,
building cross tests of current cvs fails for me with:
i386-mingw32-gcc capture.cross.o ds3d.cross.o dsound.cross.o propset.cross.o testlist.cross.o -o dsound_crosstest.exe -ldsound -lole32 -luser32 -lkernel32 -ldxguid -luuid -ldxerr8 /usr/local/lib/gcc-lib/i386-mingw32/3.2.3/../../../../i386-mingw32/lib/ libdxguid.a(dxguid.o)(.text+0x570):/usr/src/packages/BUILD/mingw-3.2/ w32api-2.5/lib/directx/dxguid.c: multiple definition of `CLSID_DirectSoundPrivate' propset.cross.o(.text+0x0):propset.c: first defined here /usr/local/lib/gcc-lib/i386-mingw32/3.2.3/../../../../i386-mingw32/lib/ libdxguid.a(dxguid.o)(.text+0x580):/usr/src/packages/BUILD/mingw-3.2/ w32api-2.5/lib/directx/dxguid.c: multiple definition of `DSPROPSETID_DirectSoundDevice' propset.cross.o(.text+0x10):propset.c: first defined here make[3]: *** [dsound_crosstest.exe] Fehler 1 make[3]: Leaving directory `/usr/src/wine/wine-mingw/dlls/dsound/tests' make[2]: *** [tests/__crosstest__] Fehler 2 make[2]: Leaving directory `/usr/src/wine/wine-mingw/dlls/dsound' make[1]: *** [dsound/__crosstest__] Fehler 2 make[1]: Leaving directory `/usr/src/wine/wine-mingw/dlls' make: *** [dlls/__crosstest__] Fehler 2
Bye Stefan
Stefan Leichter wrote:
Hello,
building cross tests of current cvs fails for me with:
i386-mingw32-gcc capture.cross.o ds3d.cross.o dsound.cross.o propset.cross.o testlist.cross.o -o dsound_crosstest.exe -ldsound -lole32 -luser32 -lkernel32 -ldxguid -luuid -ldxerr8 /usr/local/lib/gcc-lib/i386-mingw32/3.2.3/../../../../i386-mingw32/lib/ libdxguid.a(dxguid.o)(.text+0x570):/usr/src/packages/BUILD/mingw-3.2/ w32api-2.5/lib/directx/dxguid.c: multiple definition of `CLSID_DirectSoundPrivate' propset.cross.o(.text+0x0):propset.c: first defined here /usr/local/lib/gcc-lib/i386-mingw32/3.2.3/../../../../i386-mingw32/lib/ libdxguid.a(dxguid.o)(.text+0x580):/usr/src/packages/BUILD/mingw-3.2/ w32api-2.5/lib/directx/dxguid.c: multiple definition of `DSPROPSETID_DirectSoundDevice' propset.cross.o(.text+0x10):propset.c: first defined here make[3]: *** [dsound_crosstest.exe] Fehler 1 make[3]: Leaving directory `/usr/src/wine/wine-mingw/dlls/dsound/tests' make[2]: *** [tests/__crosstest__] Fehler 2 make[2]: Leaving directory `/usr/src/wine/wine-mingw/dlls/dsound' make[1]: *** [dsound/__crosstest__] Fehler 2 make[1]: Leaving directory `/usr/src/wine/wine-mingw/dlls' make: *** [dlls/__crosstest__] Fehler 2
Bye Stefan
Wine dxguid used to include those IIDs but windows doesn't so I removed them and fixed the files that used them to define the IIDs directly. Looks like the same fix needs to be done to mingw or maybe recompile your dxguid.lib.
On Fri, 23 Jul 2004, Robert Reif wrote: [...]
Wine dxguid used to include those IIDs but windows doesn't so I removed them and fixed the files that used them to define the IIDs directly. Looks like the same fix needs to be done to mingw
[...]
Exactly. I got my libdxguid.a from the following URLs a couple of days ago: http://mirzam.it.vu.nl/mingw/
I thought that was the special 'Wine edition' MinGW library but apparently not. Where can I find the special 'Wine edition'? I guess it's more likely to be updated on short order...
Should we have a link pointing to these special tools on WineHQ? Maybe on the resources page? http://www.winehq.org/site/resources
Or can we actually use this instead? http://prdownloads.sourceforge.net/wine/wine-w32api-20040505.zip?download
On Saturday 24 July 2004 01:18, Francois Gouget wrote:
Exactly. I got my libdxguid.a from the following URLs a couple of days ago: http://mirzam.it.vu.nl/mingw/
I thought that was the special 'Wine edition' MinGW library but apparently not. Where can I find the special 'Wine edition'? I guess it's more likely to be updated on short order...
It *is* the special Wine edition, but it's only today that I found some time to bring it up to date. Essential changes:
- update gcc to 3.4.1-20040711-1 - remove dxguids patch to w32api - add mlang uuids patch to w32api - update mingw-runtime to 3.3 - remove 2 patches to runtime accepted upstream
I was able to cross compile all Wine tests in current CVS. Find it here:
Should we have a link pointing to these special tools on WineHQ? Maybe on the resources page? http://www.winehq.org/site/resources
That's a good idea, though it's linked to already from here:
http://winehq.org/site/docs/wine-devel/cross-compiling-tests
Or can we actually use this instead? http://prdownloads.sourceforge.net/wine/wine-w32api-20040505.zip?download
Yes I have thought about that too. Advantage is that Wine tests are more likely to compile and link. Disadvantage is that Wine get's less testing with 3rd party headers and/or import libraries. Maybe I should do a mingw-w32api *and* a wine-w32api rpm package...
-Hans