[fdo-internals] RE: Self Build Thirdparty (curllib) on Windows

[Crispin_at_1Spatial]

OK - for the record - a bit of RTFM...

I did not have ActivePerl installed (- the OpenSSL solution throws no errors
running build_thirdparty from the command prompt so it was not apparent
until I opened the solution in VS2008).  Once I installed the latest
ActivePerl community edition (5.12.2 at the moment) things started to build
properly.

So my x86 is good for WMS.


However, x64 is not quite so healthy.  I am running builds on Win 7 x64. 
Any comments welcome...

 1) 
First off, the "-a=clean" options do not clean OpenSSL properly and you need
to manually clear out the \Thirdparty\openssl\tmp32 folder as this is shared
with x86 and x64 builds.  Ideally there would be a \tmp64 folder or the
batch files edited to del the contents on "clean" action.

 2) 
Secondly, my  "build -p=x64 -w=wms"  cannot find or use the boost lib.
LINK : fatal error LNK1104: cannot open file
'boost_thread-vc90-mt-1_34_1.lib'

Should there be an x64 build of boost?
Line 291 of \Thirdparty\build.bat seems to ensure that boost is not built
for x64 by jumping the boost solution.

 3)
Finally, when I try a  "build_thirdparty -p=x64 -w=wms"  from trunk (just
for fun!) it all goes really wrong for me - OpenSSL gets stuck.


MASM : fatal error A1000: cannot open file : tmp32\x86_64cpuid.asm

NMAKE : fatal error U1077: '"F:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\bin\x86_amd64\ml64.EXE"' : return code '0x1'

Project : error PRJ0019: A tool returned an error code from "Performing
Makefile project actions"

Done Building Project "E:\Projects\FDO\trunk\Thirdparty\openssl\openssl.sln"
(Build target(s)) -- FAILED.
-- 
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Self-Build-Thirdparty-curllib-on-Windows-tp5743435p5747448.html
Sent from the FDO Internals mailing list archive at Nabble.com.