Patch for RTT to use Xenomai from non-standard install dir

The paths for Xenomai are hard coded into RTT. This patch applies the
recommended CMake method to find libraries, etc., using the
CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH environment variables.
S

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

AttachmentSize
patch-rtt-xenomai-cmake.patch2.14 KB

Patch for RTT to use Xenomai from non-standard install dir

On Wednesday 21 January 2009 21:10:09 S Roderick wrote:
> The paths for Xenomai are hard coded into RTT. This patch applies the
> recommended CMake method to find libraries, etc., using the
> CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH environment variables.
> S

Applied on trunk. Thanks !

The user still may need to set XENOMAI_INSTALL_DIR=/path/to/...

In order to get it found.

Peter

Patch for RTT to use Xenomai from non-standard install dir

On Jan 21, 2009, at 16:33 , Peter Soetens wrote:

> On Wednesday 21 January 2009 21:10:09 S Roderick wrote:
>> The paths for Xenomai are hard coded into RTT. This patch applies the
>> recommended CMake method to find libraries, etc., using the
>> CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH environment variables.
>> S
>
> Applied on trunk. Thanks !
>
> The user still may need to set XENOMAI_INSTALL_DIR=/path/to/...
>
> In order to get it found.

FYI on my system, I just

export CMAKE_INCLUDE_PATH=/path/to/include
export CMAKE_LIBRARY_PATH=/path/to/lib
cmake ...

and it all works fine.
S

Patch for RTT to use Xenomai from non-standard install dir

On Wed, Jan 21, 2009 at 11:00 PM, S Roderick <kiwi [dot] net [..] ...> wrote:
> On Jan 21, 2009, at 16:33 , Peter Soetens wrote:
>
>> On Wednesday 21 January 2009 21:10:09 S Roderick wrote:
>>>
>>> The paths for Xenomai are hard coded into RTT. This patch applies the
>>> recommended CMake method to find libraries, etc., using the
>>> CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH environment variables.
>>> S
>>
>> Applied on trunk. Thanks !
>>
>> The user still may need to set XENOMAI_INSTALL_DIR=/path/to/...
>>
>> In order to get it found.
>
> FYI on my system, I just
>
> export CMAKE_INCLUDE_PATH=/path/to/include
> export CMAKE_LIBRARY_PATH=/path/to/lib
> cmake ...
> and it all works fine.

Agreed. And if it doesn't, I would call that a bug? Or is there a
reason (xeno-config or things like that) for which the approach
doesn't work in this case?

Klaas

Patch for RTT to use Xenomai from non-standard install dir

On Jan 22, 2009, at 03:17 , Klaas Gadeyne wrote:

> On Wed, Jan 21, 2009 at 11:00 PM, S Roderick <kiwi [dot] net [..] ...> wrote:
>> On Jan 21, 2009, at 16:33 , Peter Soetens wrote:
>>
>>> On Wednesday 21 January 2009 21:10:09 S Roderick wrote:
>>>>
>>>> The paths for Xenomai are hard coded into RTT. This patch applies
>>>> the
>>>> recommended CMake method to find libraries, etc., using the
>>>> CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH environment variables.
>>>> S
>>>
>>> Applied on trunk. Thanks !
>>>
>>> The user still may need to set XENOMAI_INSTALL_DIR=/path/to/...
>>>
>>> In order to get it found.
>>
>> FYI on my system, I just
>>
>> export CMAKE_INCLUDE_PATH=/path/to/include
>> export CMAKE_LIBRARY_PATH=/path/to/lib
>> cmake ...
>> and it all works fine.
>
> Agreed. And if it doesn't, I would call that a bug? Or is there a
> reason (xeno-config or things like that) for which the approach
> doesn't work in this case?

This works fine for me in all cases in Orocos, and is the recommended
approach by CMake. I have, however, noticed that sometimes the way
that we manipulate cache variables (and something to do with the way
we explicitly reset them on subsequent cmake runs) screws up CMake if
you rerun it. You'll notice in this patch that I worked around that
with an additional CMake variable. Without a standard approach, this
might possibly become problematic in the future ..
S