> If you *have* set SIMGEAR_DIR or other settings, I'd recommend erasing your
> build
> directory and running cmake from clean - it 'remembers' previous values in
> the build dir's cache.
Ah, that's how it's supposed to be... I've now hacked my way through by adding
the path explicitly to Fin
On 23 Nov 2012, at 12:33, Renk Thorsten wrote:
> When I change to my flightgear build directory and do
>
> cmake ../../flightgear
Use the same CMAKE_INSTALL_PREFIX for everything, and it will all work out. No
need to set SIMGEAR_DIR or anything. If you *have* set SIMGEAR_DIR or other
settin
On Fri, 2012-11-23 at 12:33 +, Renk Thorsten wrote:
> cmake ../../flightgear -DSIMGEAR_DIR:PATH=/home/fgfs/FGLib
>
Hi,
Try -
$ export SIMGEAR_DIR=/home/fgfs/FGLib \
cmake ../../flightgear
In FG/CMakeModules/FindSimGear.cmake you will find
HINTS $ENV{SIMGEAR_DIR}
Note the 'ENV', so it
On Friday, November 23, 2012 14:33:58 Renk Thorsten wrote:
> I'm just trying to get a working devel environment on my new machine, and
> I've succeeded in compiling simgear, but flightgear refuses the cmake
> configuration. Basically I want to have the simgear libs inside a user
> directory and not
I'm just trying to get a working devel environment on my new machine, and I've
succeeded in compiling simgear, but flightgear refuses the cmake configuration.
Basically I want to have the simgear libs inside a user directory and not
system-wide. So what I did is cloning the repositories, changi
5 matches
Mail list logo
