Self Build FDO 3.6 fail

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

Self Build FDO 3.6 fail

jamesgraylock
I have downloaded source code from Fdo official site, and following the document to build it by myself.
1, run setenvironment.bat
it's ok.
2, run build_thridparty.bat
it's ok.
3, run build.bat
I meet a error as below:

Project "C:\OpenSource_FDO\Fdo\FDO.sln" on node 0 (Build target(s)).
  Building solution configuration "release|Win32".
Message:
  Deleting file "C:\OpenSource_FDO\Fdo\Unmanaged\Message.tmp_Release_Win32.vcpr
  oj".
Common:
  Deleting file "C:\OpenSource_FDO\Fdo\Unmanaged\Common.tmp_Release_Win32.vcpro
  j".
Geometry:
  Deleting file "C:\OpenSource_FDO\Fdo\Unmanaged\Geometry.tmp_Release_Win32.vcp
  roj".
Project : error PRJ0019: A tool returned an error code from "Updating Assembly
Version Information for ..\Bin\Win32\Release\OSGeo.FDO.Common.dll"
Done Building Project "C:\OpenSource_FDO\Fdo\FDO.sln" (Build target(s)) -- FAIL
ED.

Does anyone know how to resolve it? Or give me some more detail about how to build fdo by myself, or anything need to pay attentions?

Thanks,
James
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

Jackie Ng
The UpdateVersion.exe under Thirdparty\util\UpdateVersion\bin is probably failing for some reason

The build logs should tell you more information. If there's no build logs, build the offending solution from within Visual Studio itself, it will write one out.

- Jackie
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

Crispin_at_Linknode
In reply to this post by jamesgraylock
Hi,

Not sure it will help for you, but I always run "build -fdo" first and then the providers I need "build -shp" etc
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

jamesgraylock
This post was updated on .
In reply to this post by jamesgraylock
I am build in x64 platform,

The error log I have taken a screen-shot, thanks.
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

jamesgraylock
In reply to this post by Jackie Ng
Jackie Ng wrote
The UpdateVersion.exe under Thirdparty\util\UpdateVersion\bin is probably failing for some reason

The build logs should tell you more information. If there's no build logs, build the offending solution from within Visual Studio itself, it will write one out.

- Jackie
Thank you Jackie, I have resolved it, but when I build them to x64 dlls, I meet another problem above when I run build_thirdparty. And a wired thing is that I couldn't run -p=x64, it show a error
"The system cannot find the batch label specified - study_params", so I set the default value to SET TYPEPLATFORM=x64 in thirdparty.bat file.

James
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

jamesgraylock
This post has NOT been accepted by the mailing list yet.
This post was updated on .
In reply to this post by jamesgraylock
There are some more screen-shot for the error when I build fdo
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

jamesgraylock
This post has NOT been accepted by the mailing list yet.
In reply to this post by jamesgraylock
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

Jackie Ng
Is this the same working dir where you previously attempted to compile for x86?

If so, you should clean (build/build_thirdparty -a=clean) the WC first (with setenvironment.bat called for that particular compiler) before attempting a fresh build targeting a different CPU.

There was some previous talk of the 3rd party projects outputting files to the same dir for x86 and x64 configurations, creating potential linking conflicts if you didn't clean before switching CPU platforms.

- Jackie
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

Greg Boone
Based on my experience, I strongly recommend you build x86 and x64 Thirdparty in separate build trees.

Greg

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng
Sent: Monday, January 30, 2012 12:44 AM
To: [hidden email]
Subject: [fdo-internals] Re: Self Build FDO 3.6 fail

Is this the same working dir where you previously attempted to compile for x86?

If so, you should clean (build/build_thirdparty -a=clean) the WC first (with setenvironment.bat called for that particular compiler) before attempting a fresh build targeting a different CPU.

There was some previous talk of the 3rd party projects outputting files to the same dir for x86 and x64 configurations, creating potential linking conflicts if you didn't clean before switching CPU platforms.

- Jackie

--
View this message in context: http://osgeo-org.1560.n6.nabble.com/Self-Build-FDO-3-6-fail-tp3887987p4349744.html
Sent from the FDO Internals mailing list archive at Nabble.com.
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

jamesgraylock
This post has NOT been accepted by the mailing list yet.
Guys,

I have try again to build x64 in a new folder, every files are new which extract from downloaded source.
But still has the same error when I build thirdparty

Thanks,
James
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

jamesgraylock
This post has NOT been accepted by the mailing list yet.
In reply to this post by jamesgraylock
There is another error when I use VS2010 command prompt
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

Jackie Ng
Did you install nasm and is it in the PATH environment variable?

http://www.nasm.us/

Your output says it's trying to find the nasm executable

- Jackie
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

jamesgraylock
This post has NOT been accepted by the mailing list yet.
Jackie,

Thanks for your advice.

I have installed the nasm, I got another error as below:



James
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

Jackie Ng
I had x64 build problems on openssl too, but I could not recall if it was this exact error.

For me I just re-ran the build scripts and openssl was successfully built. Yeah, it sounds like a dumb solution, but I'm guessing probably something in openssl or the build environment is preventing a clean build of openssl 64-bit in a single pass.

- Jackie
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

jamesgraylock
This post has NOT been accepted by the mailing list yet.
In reply to this post by jamesgraylock
Jackie,

When I run build_thirdparty.bat -a=clean, I got error below:
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

Jackie Ng
Did you call setenvironment.bat with the "VC10" parameter? As that instructs the build scripts to use the VC10 compiler instead of the (not installed?) VC9 compiler.

- Jackie
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

jamesgraylock
This post has NOT been accepted by the mailing list yet.
Jackie,

Thanks for your advice, I add VC10 that clean succuessful. But when I call build_thirdparty.bat -p=x64 again, it show another error.
Reply | Threaded
Open this post in threaded view
|

Re: Self Build FDO 3.6 fail

jamesgraylock
This post has NOT been accepted by the mailing list yet.
I call build.bat for x64 and when it built RDBMS provider has the error below, I don't if I need to install some addtional tool just like nasm, but the x86 is built successuful without any tools.