Alan,
Your bad experience is not a generality. All you have to do is set the
MSVC_3RDPARTY_DIR and hit configure again, and all the other directories should
be set automatically.
Regards,
-Fred
Alan Teeder <ajtee...@v-twin.org.uk> a écrit :
-----Original Message-----
From: MathiasFröhlich
Sent: Monday, September 05, 2011 4:28 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Cmake
Hi,
On Monday, September 05, 2011 14:47:44 Alan Teeder wrote:
> Please don´t.
>
> I reverted from VC100 to VC90 as the Cmake process was always failing.
> There is a difference between Hudson saying that all is OK with Cmake and
> Visual Studio VC100 producing working executables.
>
> This was all with the de-facto standard 3rd party package from
> ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/.
>
> I could get the system to work, but then it would all go wrong after a few
> days or weeks. On the other hand the current VC90 project files seem quite
> robust.
Then please tell what is going wrong.
This is like every piece of code lingering around in this and similar
projects. The people doing the changes do their best to make it work. But if
there is something failing on some other platform/configuration/... feedback
is
needed.
Thanks
Mathias
-----------------------------------------------------------------------------------------------------------------------------------
Mathias
I did, but I am afraid that your reply did not address my question.
When I did get it working, every time that there was a change requiring a
new set of project files, Cmake got very confused and came up with new sets
of problems.
Each time that I deleted the cache (to start afresh when cmake gave up),
cmake wanted loads of info, most of which it should have known as my
flightgear folder layout is the standard one. Boringly, I had to re-enter
the location of every simgear library, as well as openal and zlib which
already existed in the 3rd party structure.
A few more hiccups, which I can no longer remember, VS produced an
executable However this would not run and usually involved using the
depends tool to work out why FG had been made with the wrong set of
libraries.
The final straw came with the incorporation of HLA, which I never sorted
out.
VC100 is to be avoided like the plague. It even seems to have problems
linking with libraries produced with different versions of VC100.
Alan
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
