http://bugs.orocos.org/show_bug.cgi?id=911

Summary: typelib ruby extension needs to know where are boost
headers
Product: Toolchain
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: Typelib
AssignedTo: orocos-dev [..] ...
ReportedBy: arnaud [dot] degroote [..] ...
CC: orocos-dev [..] ...
Estimated Hours: 0.0

If boost is in non-standard path, the compilation of typelib ruby extension
fails with the following message:

/usr/bin/c++ -Dtypelib_ruby_EXPORTS -DWITH_DYNCALL -fPIC
-I/home/adegroot/autoproj/typelib/build -I/home/adegroot/autoproj/typelib
-I/home/adegroot/autoproj/install/include -I/usr/include/libxml2
-I/home/adegroot/autoproj/typelib/build/bindings/ruby/dyncall/include
-I/usr/lib/ruby/1.8/x86_64-linux -Wall -fno-strict-aliasing -g -g -O2 -fPIC
-o CMakeFiles/typelib_ruby.dir/ext/typelib_ruby.o -c
/home/adegroot/autoproj/typelib/bindings/ruby/ext/typelib_ruby.cc
In file included from /home/adegroot/autoproj/typelib/typelib/value.hh:6:0,
from
/home/adegroot/autoproj/typelib/bindings/ruby/ext/typelib.hh:6,
from
/home/adegroot/autoproj/typelib/bindings/ruby/ext/typelib_ruby.cc:1:
/home/adegroot/autoproj/typelib/typelib/registry.hh:5:32: fatal error:
boost/shared_ptr.hpp: Aucun fichier ou dossier de ce type
compilation terminated.

In the top CMakeLists.txt, the detection and header inclusion of boost are
after the decision to build ruby extension. It must be before, as ruby
extension depends indirectly on boost. See the attached patch for a fix.