On Wed, Apr 2, 2008 at 2:51 PM, John Klehm xixsimplicityxix@gmail.com wrote:
On Fri, Mar 28, 2008 at 6:05 AM, John Klehm xixsimplicityxix@gmail.com wrote:
Well let me know how this works for you. I'll refactor my script a bit later today but for right now you have to run this one after the winetest script, as this one counts on the environment that the
Here's the refactored script [1]. With some inspiration from winetricks ;)
Example uses: $crossbuild_tricks winetest
$crossbuild_tricks d3d => builds d3d8,d3d9,wined3d, libwine
$crossbuild_tricks test cabinet => use test verb for individual tests
$crossbuild_tricks dll wintrust => use dll verb for individual dlls
First release and I've tested it some, seems to work but let me know if it breaks for you.
Regards, John
Updated version of crossbuild_tricks: http://klehm.net/wine/crossbuild_tricks.sh
Changes:
-improved build time: builds only the minimum required targets now.
New verbs: libs => build just the import libs (*.a). Puts them in wine-pe/libs/wine as usual. alldlls => build all possible dlls. Copies them to wine-pe/binaries for easy downloading.
Dlls known not to cross build: dbghelp dnsapi gdi32 glu32 icmp iphlpapi kernel32 msvcrt ntdll opengl32 rpcrt4 secur32 shell32 winex11.drv wininet winmm ws2_32
distclean => clean up the wine-native and wine-pe dirs and run distclean in wine-src (a "wash me clean of this dirty script" verb ;)
Use the patch I sent in the other mail that adds mingw like no op exception stuff if you really need to cross build crypt32 (maybe others) that complain about missing __try etc.
Any problems let me know.
Enjoy, John