Andy Ross wrote:
Brian Thomason wrote:
Perhaps I wasn't clear enough. I should have stated that I am
attemtping to build 0.9.9 using the debian source package framework
for 0.9.8, where the .a files are converted to shared object files.
Apologies for my joking at your expense, I didn't notice your email
address. :)
;-)
Hrm... Why is debian shipping shared libraries for SimGear? As
discussed, that is not the intended deployment mode for the upstream
package (us!), so it seems awfully strange for debian (or Linspire?)
to be making its own decisions there. Does it do the same for plib?
Yes. Debian policy, I believe.
I think most of us would honestly prefer that if Linspire users are
going to install a FlightGear binary, it match the ones that we are
developing on as closely as practical.
Works for me. I wasn't building it this way to break upstream's way of
doing things - We just leverage Debian as much as possible and try to
deviate as little as possible, but in this case, it isn't a big deal.
SimGear really isn't designed to be a shared library anyway -- the
various libsg*.a files just match the directory structure of the
source code. As Alex pointed out, they have complicated dependency
relationships that are going to be difficult to manage.
I'll just repackage the whole thing. I tried manually adding the libs
to the linker, and got some of the errors to go away, but others sprang up.
Thanks again for the help. (Very fast responding, helpful community you
have here)
-Brian
Andy
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
