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

2013-02-15 Thread James Turner
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

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

2013-02-15 Thread ys
Hi James Thanks, yes, am aware of this kind of separation. But I thought: Why does cmake configuration make it possible to link against an osg include and lib dir for every part, while simgear has only a an option for headers and not the libs ?. And then when you set the simgear include dir,

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

2013-02-15 Thread Arnt Karlsen
On Fri, 15 Feb 2013 08:48:59 +, James wrote in message 954f9f95-7614-4c0e-a82f-3b589fa4e...@mac.com: 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

[Flightgear-devel] CMake question simgear include option

2013-02-14 Thread HB-GRAL
Hi Ehrm, cmake, I tried to link against another simgear but I can only link against headers, not the libs? When I have another simgear in (i.e. default path) installed it takes the headers from include definition, but the libs from first path? Or do I miss a CMake option? With simple