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

Greg Boone greg.boone at autodesk.com
Tue Nov 16 14:04:09 EST 2010

When OpenSSL is compiled, it copies files to the following location as a part of its build process:


Check to see if these files exist. 

I recommend cleaning up the generated files in the openssl directory under thirdparty, are re-building the entire openssl solution.


Mixing Win64 and Win32 builds under a single source tree may also prove to be problematic. 


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Crispin_at_1Spatial
Sent: Tuesday, November 16, 2010 11:06 AM
To: fdo-internals at lists.osgeo.org
Subject: [fdo-internals] RE: Self Build Thirdparty (curllib) on Windows


Poor case reporting by me - I do call what you suggest:

build_thirdparty -w=fdo -w=wms

But get the errors - this is on a SVN check-out version that implies it is
all OK.
Am I the only one?  I have seen it on two machines so must be something I am
missing in my general setup.

If I launch the "...Thirdparty\libcurl\lib\curllib.sln" in MSVC2008 then I
get the same message.


build_thirdparty -w=fdo      OK
build_thirdparty -w=gdal      OK

build -w=fdo      OK
build -w=gdal      OK

View this message in context: http://osgeo-org.1803224.n2.nabble.com/Self-Build-Thirdparty-curllib-on-Windows-tp5743435p5744348.html
Sent from the FDO Internals mailing list archive at Nabble.com.
fdo-internals mailing list
fdo-internals at lists.osgeo.org

More information about the fdo-internals mailing list