On Sat, 2010-07-24 at 09:27 -0700, cas...@mminternet.com wrote:
[snip]
> t...@tower SimGear-2.0.0]# ./configure 
> --with-boost=/usr/src/boost_1_43_0/boost
> 
> Strange, for some reason that does not appear to work in that the test for
> boost points to "/usr/include/boost_1_43_0/boost/include"
[snip]
> At any rate, problem solved

Hi John,

Glad you got it working without any 'patching' ;=))

Unfortunately boost does not seem to 'obey' the de facto
auto-tool path pragma... that is :-
   headers in <path>/include
 libraries in <path>/lib
And the 'standard' path will be '/usr', or 'usr/local',
as you show in part...

When you unpack boost 1.43.0 tar.gz into <somewhere>, it
puts its headers in <somewhere>/boost_1_43_0, that is
like <somewhere>/boost_1_43_0/boost/version.hpp, and when
you build the boost libraries, they are staged (uninstalled)
in - <somewhere>/boost_1_43_0/stage/lib...

Then you should do the configure with -
 --with-boost=<somewhere>/boost_1_43_0
no addition...

The AX_BOOST_BASE macro then overcomes most of this difference
between where the 'standard' auto-tools would look, and
where boost likes to put things, and my patch fixes this
for some other cases...

And this is similar even if you use the svn boost trunk,
or some other svn tag...

Anyway, all is well if you got something working ;=))

Regards,

Geoff.



------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to