[Bf-committers] Windows cross-compile fails with SCons
nathan at letworyinteractive.com
Sun Nov 14 21:28:58 CET 2010
-----BEGIN PGP SIGNED MESSAGE-----
On 14.11.2010 3:35, Caleb wrote:
> Cross-compiling a 32-bit build on 64-bit Windows seems to have some
> linking problems. I am using a 32-bit version of Python for this and
> have my VS environment set to 32-bit. Could it be some kind of
> Linking program ==> 'makesdna.exe'
> Compiling ==> 'rna_access.c'
> fatal error LNK1112: module machine type 'x64' conflicts with target
> machine type 'X86'
> scons: *** [C:\Blender\build\blender25-win32\makesdna.exe] Error 1112
> Compiling ==> 'makesrna.c'
Hmm, this error really only happens when you secretly/accidently use a
64bit Python version after all. Make absolutely sure your Python is
32bit. From the build paths you cannot tell, because you have overriden
those in a user-config.py/custom config. Also, if you use the same build
paths for 32bit and 64bit, it is probably a good idea to run a scons
with clean target after all. Even better is to use custom configurations
for different bitnesses.
I use two different configurations, called graphicall_32b and
graphicall_64, both pointing to different BF_BUILDDIR and BF_INSTALLDIR.
I activate them on command-line by passing them to scons with
BF_CONFIG=graphicall_32b and BF_CONFIG=graphicall_64b respectively.
This works, I build many times a day 32bit versions of Blender on my
64bit Win7 Ultimate.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the Bf-committers