Hi John, Erik, Jari, Sid, Curt, Csaba, et al
Thanks Erik. cvs updated, and all works in
my Ubuntu 64-bits... and remember I use
a 'non-standard' local prefix OSG install,
so I can link and run against different
OSG versions at will...
Your addition of -
AC_CHECK_LIB(osg,osgGetVersion, ,
[AC_MSG_ERROR(OpenSceneGraph library not found.)],)
etc for each OSG library looks great, and glad you
brought osgFX in from the cold ;=)).
Of course John, and perhaps others, will feel -
"OpenSceneGraph library not found."
is too brief, not informative enough, does not
really 'help' with the problem, will leave Joe
User in the cold ;=)), but I think it is fine,
and to the point.
And to those who MAY forget, or not know,
or understand, after this cvs update you
_MUST_ start with the autogen.sh step, to
re-generate the 'configure' script.
In my case, to be REAL SURE I am using the
new stuff, I do, in fgfs/source :-
$ rm -vf configure
$ rm -r -vf autom4te.cache
$ rm -vf config.log
$ rm -vf Makefile
because I have been caught out before ;=))
Jari, I too would like to add more
information in the summary at the end of
FG configure.ac. And most certainly, when
I have a problem, that is sometimes how I
track it down. But in general there seems
some resistance, reluctance to do this...
To be fair, we do have much MORE info
there than I see in many, many other .ac
(or .in) files...
Sid, I think you would need to use -
sudo make install_ld_conf
which adds an openscenegraph.conf file to
the /etc/ld.so.conf.d folder, with the line -
${CMAKE_INSTALL_PREFIX}lib${LIB_POSTFIX}
but have never tried this...
John, so all is revealed ;=))
Q: Why you would point out a problem in
linking in FG tests and then look in
simgear's config.log?
Your page item :-
http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-64bit
is about linking the 'tests/est-epsilon' binary.
This is only in flightgear... look in FG,
specifically fgfs/source/config.log!
In general -
(a) Do NOT confuse header (include) checks
with library function (lib) checks. They are
unrelated, and look in different places.
(b) Do NOT confuse compiling/linking a
'library' - simgear, with compiling/linking
an executable - fgfs, est-epsilon, etc. There
are some BIG differences.
As Csaba points out, while building a libraries,
like SG, only the 'includes' are needed. Libraries
do not 'link' with libraries. The libraries are only
needed for the final binary executable, fgfs,
tests, etc linking.
And of course, if they are 'shared' libraries,
as opposed to 'static' libraries, then they will
also need to be found at execution runtime...
$ export LD_LIBRARY_PATH=/path/to/lib[:/other/paths]
can be used to expand the search for the 'shared'
libraries, or, as mentioned, more permanently
through the ld.so.conf.d folder...
It is clear the OSG install, installs its
headers in the native, standard, (correct) place -
"$prefix/include". So that is ok. They are
found...
And all this has only been about is the fact
that it installs its libraries in a non-native,
non-standard place, "$prefix/lib64"! But can
be instructed _NOT_ to do this with a cmake
config option -D LIB_POSTFIX=
So, in your case you are pointing out that the
OSG headers can be found. Never said they couldn't.
We only search for one OSG header in both SG & FG
configure.ac, and that is the <osg/Version> header.
eg - AC_CHECK_HEADER(osg/Version)
My statement was only about finding the OSG
_LIBRARIES_, only in FG configure.ac... so will
NOT repeat what is true ;=))
> Maybe I have overlooked something ...
Hell YES!
> but IMHO whatever it is, Joe User is likely
> to overlook it also.
As you suggested, do _NOT_ be so quick to put
Joe User down ;=)) He may be smarter than you
think.
I hope this closes this 'heavy' issue ;=))
Regards,
Geoff.
------------------------------------------------------------------------------
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
