Re: [Flightgear-devel] CMake question simgear include option

[Arnt K. <ar...@c2...>]

On Fri, 15 Feb 2013 08:48:59 +0000, James wrote in message 
<954...@ma...>:

> 
> On 14 Feb 2013, at 18:58, HB-GRAL <fli...@sa...> 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

..these above (SG&FG) are your one git source tree?

> 
> 		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 dist & dist2 are 2 separate build and install trees that 
you feed from your one git tree?

> 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

-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.