Ok -D LIB_POSTFIX=
worked fine inside my script. Maybe this is
due to the shell removing the "" if done at
a command line, but not if inside a script???
In the cmake_install.cmake file it now has :-
FILE(INSTALL DESTINATION "${CMAKE_INSTALL_PREFIX}/lib/pkgconfig" TYPE
FILE FILES...
But cmake should have seen the length of ="" was
really zero content...
Anyway BINGO! They installed in my "$prefix/lib" ;=))
No 'link' step required...
SUCCESS! Another small step for mankind, no, no...
--------------------
John, I do not remember anyone suggesting 'you'
wrongly put OSG into 'lib64'. We all agree, and I
have shown the cmake output, that TELLS YOU THIS!
WARNS YOU UP FRONT that this was going to happen.
I still can not exactly understand you want
from the FG ./configure, and actually you really
mean autogen.sh, since this is when 'configure'
script is created, from configure.ac, and other
things...
And in my book, if Joe User is using linux/unix
he _IS_ a programmer in a general sense, and is
most certainly not an idiot.
I would NOT yet foist *nix on my wife for
example, not because she is an idiot - quite
the contrary ;=)) - but because she is NOT yet
prepared to be a 'programmer'. To have to fiddle
around, change and understand things...
You jump on this out-of-the-box, but to me
NOTHING in *nix is out-of-the-box! There is
almost NOTHING I have done that did NOT require
me, at some level, to get into 'programming'.
To move something, to change the permissions,
create links, learn about SWITCHES to this,
to that tool, etc, etc, etc... AND some of
these absolutely require superuser status, at
least temporarily through 'sudo'.
In fact one might say that this is the FUN
of *nix ;=))
Even to install it, I had to remind myself a
lot more about HDD partitions, had to answer
questions I most certainly knew nothing about...
the only thing that got me initialized was
a reasonable set of defaults - like SG/FG
has a reasonable set of defaults.
But back to configure... yes it sometimes
generates little 'test' programs, compiles and
runs these, and depending on the result
either of the compile, or the running, will
make certain decisions.
So sometimes, it is due to the fact that this
tiny test program FAILED to compile, is the
test itself. But whether we set the configure
script to ABORTS at this point, with message,
largely depends on so many other things...
But that seems beside the point. The configure
script _DID_ tell you it could _NOT_ find the
OSG libraries - you just ignore it. You did not
heed its clear indication that you were headed
into trouble...
So it seems even if we had some MORE documentation
in SG/FG to say - CHECK THE CONFIGURE SCRIPT
FINDS ALL THE NECESSARY LIBRARIES - there
can be a problems specifically with OSG
libraries, and where they are installed -
you would have IGNORED it, the same way you
ignored the content of config.log, which
TOLD YOU it was having a problem.
And how much documentation should we have
in SG/FG about downloading, configuring,
compiling, installing prerequisites packages
depends. Some would say it is sufficient to
say SG/FG depend on OSG say 2.8.1 or higher
(or whatever the number is)...
Others like me, usually want a little more
than this. And now that we know about it,
and have 'solved' it, this OSG cmake lib64
could/should be mentioned, but none of us
want to attempt to fully document all the
options on each prerequisite - you should
be prepared to read their documentation.
So what more do you want us to do???
Here we are TRYING hard to help you, and
you seem to be yelling something. Before your
long rant I was going to say ---
==============
And after John tests and checks this, I hope he will
_REMOVE_ this suggested configuration 'snafu' from
his BUG list ;=()
There may be others issues, but this 'lib64' item
seems closed - bludgeoned to death ;=))
Although I still see no particular problem in slightly
improving the FG configure.ac script, and README.OSG,
it now does NOT seem so essential...
The build quickly aborted on not finding -losgFX,
and a review of the config.log would show in fact
NO OSG libraries had been found, which should alert
one to an OSG 'installation' issue.
That is, is this sufficient TLC for now? ;=)) We
have the silver bullet - cmake -D LIB_POSTFIX=!
============
But now! Wow, if in the mind to, the number of
posts on this thread will mount exponentially ;=))
I will opt out of it for now, with the problem
solved.
Who ever claimed 'that Joe User can install OSG
and FG from source "out of the box"' is a liar,
if not an idiot to boot ;=)) Like all good things,
it comes at a price, with considerable effort,
but I and others do our best to HELP.
John, if you want more help, perhaps write to
me direct off list, and I WILL do my VERY best to
quietly explain...
Regards,
Geoff.
PS: Have updated my makefg accordingly -
http://geoffair.net/tmp/makefg
to version 1.1.5
------------------------------------------------------------------------------
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
