RE: [Flightgear-devel] SimGear as shared lib
> 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 libraries > > right from the SimGear build directory. > > or modify make install so that it emulates "cp -p " > Yes. I tried to do that once and just lost interest before getting it working (didn't take long). Really though, I find it annoying to install a library that is statically linked by only one application into my lib directories. There's already way too much useless crapola and redundancy-because-everyone-wants-to-start-their-own-project-these-days in the typical linux distro's library directory(ies) these days. Which is why I have them installing in a non-default prefix location. Just a thought... :-) Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] SimGear as shared 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 build directory. or modify make install so that it emulates "cp -p " Norman ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] SimGear as shared lib
> 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 timestamps on the header files in SimGear change. That's actually a good thing and isn't fixed one way or the other by building SimGear so. Well...I guess the only difference is you have to delete fgfs to get it to relink for you. The make install does a "copy" of thoese headers which means new timestamps even if they haven't changed. So if you avoid doing that by whatever method you'll be fine. Generally if I know there hasn't been an api change I'll just use a copy command that only copies updated libraries to the lib directory. Then I delete the fgfs executable and relink it. 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 build directory. Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] SimGear as shared lib
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 static libs, especially since rebuilding SimGear doesn't take that long - compared to FlightGear, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] SimGear as shared lib
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 Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
