On 14 Feb 2013, at 18:58, HB-GRAL <flightg...@sablonier.ch> wrote:
> With simple -DCMAKE_INSTALL_PREFIX it finds the "custom location" of the
> headers and libs without any other option, but when I add
> -DSIMGEAR_INCLUDE_DIR=/path/to/include it takes the headers from this
> location, but not the libs anymore, it falls back to another simgear
> install on my system (which is in path). So I need to remove default
> simgear from my path, and then cmake works perfect.
>
> Sometimes I wonder with what things I can struggle with flightgear
> compilation and why only ME have such problems. ;-)
Avoid setting the include path directly, would be my advice.
If you want to use different simgear builds, then keep the completely separate.
Eg, I have:
~/FGFS/
simgear
flightgear
fgBuild # configured with
CMAKE_INSTALL_PREFIX=~/FGFS/dist
sgBuild # configured with
CMAKE_INSTALL_PREFIX=~/FGFS/dist
dist
fgBuild2 # configured with
CMAKE_INSTALL_PREFIX=~/FGFS/dist2
sgBuilld2 # configured with
CMAKE_INSTALL_PREFIX=~/FGFS/dist2
dist2
And this works fine for me, the different diet trees can have totally different
version / config options since there is no overlap at all.
James
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
