Use of CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH directives are ignored. Instead, install paths for each individual component must be fully specified
{{{
ccmake -DCMAKE_INSTALL_PREFIX=/opt/install -DMATRIX_LIB=boost -DRNG_LIB=boost -DMATRIX_INSTALL=/opt/local -DRNG_INSTALL=/opt/local -DCPPUNIT_INSTALL=/opt/local ../..
}}}
instead of (for BASH, picking up libraries from MacPorts)
{{{
export CMAKE_INCLUDE_PATH=/opt/local
export CMAKE_LIBRARY_PATH=/opt/local
ccmake -DCMAKE_INSTALL_PREFIX=/opt/install -DMATRIX_LIB=boost -DRNG_LIB=boost ../..
}}}
We have corrected several of these issues in RTT and OCL over the last few months. How do people feel about having this fixed in BFL? It would bring it inline with the other Orocos projects.
Cheers
S
Does not honor CMAKE directives for include and library paths
Use of CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH directives are ignored. Instead, install paths for each individual component must be fully specified
{{{
ccmake -DCMAKE_INSTALL_PREFIX=/opt/install -DMATRIX_LIB=boost -DRNG_LIB=boost -DMATRIX_INSTALL=/opt/local -DRNG_INSTALL=/opt/local -DCPPUNIT_INSTALL=/opt/local ../..
}}}
instead of (for BASH, picking up libraries from MacPorts)
{{{
export CMAKE_INCLUDE_PATH=/opt/local
export CMAKE_LIBRARY_PATH=/opt/local
ccmake -DCMAKE_INSTALL_PREFIX=/opt/install -DMATRIX_LIB=boost -DRNG_LIB=boost ../..
}}}
We have corrected several of these issues in RTT and OCL over the last few months. How do people feel about having this fixed in BFL? It would bring it inline with the other Orocos projects.
Cheers
S
_______________________________________________
I hereby promise not to top-post on the
BFL mailing list
BFL [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/bfl
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Does not honor CMAKE directives for include and library paths
[[I had my BFL subscription disabled by accident for a while, so I post this via the forum. Sorry for the loss of context for people reading this on the ML: It deals with more portable/robust cmake macros for bfl's build system]
But yes, we (I can only speak for myself, but I think I might be able to convince the maintainer :-) sure are interested in having the portable approach as we did for RTT and OCL with the mac os x port.
I had already noticed this in
In that respect we maybe should retitle
Your patches are welcome :-)
Does not honor CMAKE directives for include and library paths
On Mon, Dec 1, 2008 at 5:23 PM, <klaas [dot] gadeyne [..] ...> wrote:
> [I had my BFL subscription disabled by accident for a while, so I post this
> via the forum. Sorry for the loss of context for people reading this on the
> ML: It deals with more portable/robust cmake macros for bfl's build system]
>
> But yes, we (I can only speak for myself, but I think I might be able to
> convince the maintainer :-) sure are interested in having the portable
> approach as we did for RTT and OCL with the mac os x port.
> I had already noticed this in
> In that respect we maybe should retitle
> Your patches are welcome :-)
Moreover, there seem to be some problems with the forum2ML conversion
of URL's. Please check
for the full story.
Klaas
_______________________________________________
I hereby promise not to top-post on the
BFL mailing list
BFL [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/bfl
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Does not honor CMAKE directives for include and library paths
Proposed patch attached. Works for Mac with boost in Macports, and Ubuntu with boost.