> From: "Norman Vine"
>
> Jim Wilson writes:
> >
> > I think the real issue is that SimGear shouldn't be installed anywhere
> > ever, because it isn't a shared library (and
> > doesn't need to be). It seems like it should be possible to fix the fgfs
> > build setup so that it just links lib
Jim Wilson writes:
>
> I think the real issue is that SimGear shouldn't be installed anywhere ever,
> because it isn't a shared library (and
> doesn't need to be). It seems like it should be possible to fix the fgfs
> build setup so that it just links libraries
> right from the SimGear buil
> From: Karsten Krispin
>
> Hi
>
> just a small question: is it hard to include simgear as shared libs?
> When you want to change something in simgear you have to recompile fgfs. that
> needs pretty too long.
>
> Or is there a trick?
>
Rebuilding modules in fgfs only happens when the timestam
Hello Karsten,
Karsten Krispin wrote:
> just a small question: is it hard to include simgear as shared libs?
No, it's not dificult at all. But you probably don't _want_ to, because
changes in FlightGear sometimes relate to changes in SimGear so you
have to rebuild SimGear anyway.
I'd stick to st
Hi
just a small question: is it hard to include simgear as shared libs?
When you want to change something in simgear you have to recompile fgfs. that
needs pretty too long.
Or is there a trick?
Karsten Krispin
___
Flightgear-devel mailing list
Fligh
