From: Curtis O. <cur...@gm...> - 2007-07-24 14:47:10
|
On 7/24/07, Melchior FRANZ <mf...@ao...> wrote: > > ... it's a solution that is in fact about turning fgfs into shared libs > ... For whatever it's worth, we went down the "libtool" path for a while in FlightGear and decided at the time that the headaches a weirdness of libtool simply wasn't worth the effort. The build system got much simpler when we moved to static libs. That's not to say that we can't find some advantages to shared libs, generally there aren't too many, but in the case of building several versions of the FG binary, I can see the benefit. But on the whole, I'd really prefer to stick with static libs, and would really prefer to avoid libtool. For instance, I always had a little trouble getting gdb to work on a wrapper script. :-) Libtool for those that don't know, imposes a couple layers of indirection and wrapper scripts on top of everything so that you can "sort of" run the resulting executable out of your build tree without installing it first, but life starts to get more difficult when you start trying to do debugging, or need to figure out what's really going on with your libraries, often times it's very difficult to find the actual library since libtool is pretty good at hiding everything from you. I suppose I ended up on my soap box again here, sorry about that. :-) I have no problem with people using libtool for genuine shared library packages; it can make a lot of sense there. But for FlightGear/SimGear we found that it ended up causing more headaches than it cured. Regards, Curt. -- Curtis Olson - University of Minnesota - FlightGear Project http://baron.flightgear.org/~curt/ <http://baron.flightgear.org/%7Ecurt/> http://www.humanfirst.umn.edu/ http://www.flightgear.org Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d |