Well, it seems there _ARE_ already 8 checks
for OSG libraries, but with no action if-found,
or if-not-found :-
AC_CHECK_LIB(osg,osgGetVersion)
AC_CHECK_LIB(osgUtil,osgUtilGetVersion)
AC_CHECK_LIB(osgDB,osgDBGetVersion)
AC_CHECK_LIB(osgText,osgTextGetVersion)
AC_CHECK_LIB(osgGA,osgGAGetVersion)
AC_CHECK_LIB(osgViewer,osgViewerGetVersion)
AC_CHECK_LIB(osgSim,osgSimGetVersion)
AC_CHECK_LIB(osgParticle,osgParticleGetVersion)
So if not found the only effect would be an output
to config.log of not found...
Then for some unknown reason osgFX is added
unconditionally!!!
LIBS="$LIBS -losgFX $opengl_LIBS"
We later do a check for the OSG version header -
AC_CHECK_HEADER(osg/Version)
and ABORT if this is NOT found, but that is
a "$prefix/include" check, not 'lib'.
So it seems we only need -
(a) osgFX to be checked like the others,
(b) put a consequence if found or not found.
Ref:
AC_CHECK_LIB(library, function, [if-found],
[if-not-found], [other-libraries])
In fact, it would seem sufficient to just
check the primary 'osg' library, since it
would be rare case indeed if it was found,
and the others not... but this is debatable...
Something like :-
OSG_OK="no"
then the per host type checks -
...
AC_CHECK_LIB(osg,osgGetVersion,[OSG_OK="yes"])
...
Then -
if test "$OSG_OK" != "yes"; then
echo
echo "You *must* have the OSG libraries installed on"
echo "your system to build and run FlightGear!"
echo "Have they been installed in a 'lib64' folder?"
echo
echo "Please see README.OSG for more details."
echo
echo "configure aborted."
exit
fi
And maybe along with this, the README.OSG could
be updated, and beefed up with more information,
especially about this known 'lib64' cmake install
situation.
But after doing this I bounce back to the
'problem'. This configure.ac check does _NOT_ in any
way fix the 'problem' that OSG cmake can use a
non-standard 'lib64' directory.
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, and it not
even wholly sufficient to search for 'no', since some
no's are ok.
But MOST CERTAINLY, when a compile/link error occurs,
it should be one of the first files carefully scanned.
And to be sure, this is NOT a FG 'configuration snafu'
as the earlier subject suggests!
HTH
Regards,
Geoff.
PS: Thanks Martin. Will try the -D LIB_POSTFIX=""
and maybe that is the silver bullet ;=))
------------------------------------------------------------------------------
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
