Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac

2010-02-16 Thread John Denker
On 02/16/2010 01:45 PM, John Denker wrote: OK, I think we can put this sub-issue to bed. I fixed it so that compiling and installing simgear no longer requires the OSG or OpenThreads runtime libraries. The *.h header files are still required. This turned out to be easier than I thought it would

Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac

2010-02-16 Thread John Denker
On 02/08/2010 08:34 AM, Geoff McLane wrote: > you seem to be yelling something. On 02/16/2010 11:47 AM, Geoff McLane wrote: > It seems WHATEVER the reason is, IF it involves > a SimGear AC_CHECK_LIB() then _REMOVE_ the > AC_CHECK_LIB() from SG configure.ac ;=)) > > There is no reason to check

Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac

2010-02-16 Thread Erik Hofman
Geoff McLane wrote: > It seems Erik's previous patch to SG configure.ac > did remove some Apple framework library checks, > but did not go far enough IMHO to REMOVE ALL > AC_CHECK_LIB() in a 'library' build. > > That is, remove the check - > -o "x$ac_cv_lib_OpenThreads_OpenThreadsGetVersion" != "x

Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac

2010-02-16 Thread Geoff McLane
On Mon, 2010-02-15 at 14:59 -0700, John Denker wrote: > The reason for fussing with SG first is simple: Again, thanks Erik for patching the SG patch ;=)) Have yet to update and try SG again, but... It seems WHATEVER the reason is, IF it involves a SimGear AC_CHECK_LIB() then _REMOVE_ the AC_CHECK

Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac

2010-02-15 Thread John Denker
On 02/15/2010 11:53 AM, Geoff McLane wrote: > Just did a full SG cvs update, and this > acinclude.m4 patch _BREAKS_ the SG build for me! OK. It's a bug. Thanks for testing. Here's the patch. Please try again. The reason for fussing with SG first is si

Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac

2010-02-15 Thread Geoff McLane
On Sun, 2010-02-14 at 15:22 +0100, Erik Hofman wrote: > John Denker wrote: > > In this case it appears that adding about five lines > > of code to acinclude.m4 will remove the need for at > > least five paragraphs of documentation. It turns > > out to be quite possible to each the configuration

Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac

2010-02-14 Thread Erik Hofman
John Denker wrote: > In this case it appears that adding about five lines > of code to acinclude.m4 will remove the need for at > least five paragraphs of documentation. It turns > out to be quite possible to each the configuration > system to search lib64. Both patches have been committed to C

Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac

2010-02-12 Thread John Denker
On 02/12/2010 10:00 AM, Geoff McLane wrote: > > RE: README.OSG UPDATE > > I have now beefed up the FG README.OSG > information > > I think I have tried to cover everything, > very carefully! Thank you for your constructive contributions to the configuration system, both in terms of debugg

Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac

2010-02-12 Thread Geoff McLane
Hi, Again thank you Erik for updating the configure.ac files... This continues to work fine... RE: README.OSG UPDATE I have now beefed up the FG README.OSG information per the attached patch. I think I have tried to cover everything, very carefully! But someone in the 'know' should check that

Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac

2010-02-08 Thread Martin Spott
Geoff McLane wrote: > It _ONLY_ gives an early indication, something which > could have been _SEEN_ had the config.log been read! I > know, the config.log is long and boring, [...] Nah, 'configure' also prints a nicely readable status to STDOUT, so, for these simple cases like OSG libraries not b