leee wrote:
> But isn't one of the tasks of ./configure to test that it can find
> the libs it needs, and isn't this the real problem?
Yup, and if it doesn't find OSG libraries, then it'll be going to write
approx. eight messages in sequence about OSG libraries not being found.
The only point which might be debatable here is wether you'd expect
'configure' to exit ungracefully at this point for those users who
don't care to understand 'configure's output. BUT those who don't are
probably not the primary target group for compiling FlightGear and all
it's dependencies from source.
BTW, FlightGear's 'configure' behaves similarly wrt. other libraries -
seems to be like being the FlightGear way of dealing with missing
libraries,
Martin.
P.S.: The compile-time linker on Debian/Lenny/AMD64 is happily going to
pick the libraries from /usr/lib64/ if you move the files there.
You just have to point the runtime-linker at the directory in
order to start FlightGear.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
