Examples, tutorials and help

I have put another example up, this one concentrating on what I consider to be Orocos' best, most undocumented feature. That of naming connections, not ports, when deploying components. Incredibly useful, and not documented anywhere ... :-(

http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-aka-orocos-best-kept-secret

When the website accepts .bz2 files, I will upload all files required.

HTH
Stephen

Examples, tutorials and help

I have updated the toolkit/transport plugin example on the wiki, and
also added a working tarball of all files. In particular, see
compatability, assumptions and limitations sections.

Also, this is still a work in progress - still have to add operators,
and XML file read/write.

HTH
S

Examples, tutorials and help

On Wed, Jul 22, 2009 at 04:41, <kiwi [dot] net [..] ...> wrote:
> I have put another example up, this one concentrating on what I consider to be Orocos' best, most undocumented feature. That of naming connections, not ports, when deploying components. Incredibly useful, and not documented anywhere ... :-(
>
> http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-ak...
>
> When the website accepts .bz2 files, I will upload all files required.

Done. Your (and every other Orocos developer's) upload limit is 10MB
in total and 1MB per file.

Peter

Examples, tutorials and help

On Jul 22, 2009, at 05:39 , Peter Soetens wrote:

> On Wed, Jul 22, 2009 at 04:41, <kiwi [dot] net [..] ...> wrote:
>> I have put another example up, this one concentrating on what I
>> consider to be Orocos' best, most undocumented feature. That of
>> naming connections, not ports, when deploying components.
>> Incredibly useful, and not documented anywhere ... :-(
>>
>> http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-ak...
>>
>> When the website accepts .bz2 files, I will upload all files
>> required.
>
> Done. Your (and every other Orocos developer's) upload limit is 10MB
> in total and 1MB per file.

Fantastic, thanks Peter. I've uploaded buildable tarballs for both
examples.

So ... any chance we can add .cpf to the list of accepted extensions?
(and probably .osd and .ops as well, to round out the typical names
for Orocos data files).

Cheers
Stephen

Examples, tutorials and help

On Wed, Jul 22, 2009 at 13:41, Stephen Roderick<kiwi [dot] net [..] ...> wrote:
> On Jul 22, 2009, at 05:39 , Peter Soetens wrote:
>
>> On Wed, Jul 22, 2009 at 04:41, <kiwi [dot] net [..] ...> wrote:
>>>
>>> I have put another example up, this one concentrating on what I consider
>>> to be Orocos' best, most undocumented feature. That of naming connections,
>>> not ports, when deploying components. Incredibly useful, and not documented
>>> anywhere ... :-(
>>>
>>>
>>> http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-ak...
>>>
>>> When the website accepts .bz2 files, I will upload all files required.
>>
>> Done. Your (and every other Orocos developer's) upload limit is 10MB
>> in total and 1MB per file.
>
> Fantastic, thanks Peter. I've uploaded buildable tarballs for both examples.
>
> So ... any chance we can add .cpf to the list of accepted extensions? (and
> probably .osd and .ops as well, to round out the typical names for Orocos
> data files).

I added .cpf back then as well, .osd and ops is now present too.

Peter

Examples, tutorials and help

On Jul 22, 2009, at 08:55 , Peter Soetens wrote:

> On Wed, Jul 22, 2009 at 13:41, Stephen Roderick<kiwi [dot] net [..] ...>
> wrote:
>> On Jul 22, 2009, at 05:39 , Peter Soetens wrote:
>>
>>> On Wed, Jul 22, 2009 at 04:41, <kiwi [dot] net [..] ...> wrote:
>>>>
>>>> I have put another example up, this one concentrating on what I
>>>> consider
>>>> to be Orocos' best, most undocumented feature. That of naming
>>>> connections,
>>>> not ports, when deploying components. Incredibly useful, and not
>>>> documented
>>>> anywhere ... :-(
>>>>
>>>>
>>>> http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-ak...
>>>>
>>>> When the website accepts .bz2 files, I will upload all files
>>>> required.
>>>
>>> Done. Your (and every other Orocos developer's) upload limit is 10MB
>>> in total and 1MB per file.
>>
>> Fantastic, thanks Peter. I've uploaded buildable tarballs for both
>> examples.
>>
>> So ... any chance we can add .cpf to the list of accepted
>> extensions? (and
>> probably .osd and .ops as well, to round out the typical names for
>> Orocos
>> data files).
>
> I added .cpf back then as well, .osd and ops is now present too.
>
> Peter

LOL ... this is from the FindOrocos-RTT.cmake file in the quicky
project.

&#10;-- Looking for RTT version v1.6.0&#10;CMake Error at config/FindOrocos-RTT.cmake:85 (MESSAGE):&#10;  rtt-config.h reports version 1.10.99 &lt; required version 1.6.0&#10;Call Stack (most recent call first):&#10;  CMakeLists.txt:17 (find_package)&#10;

Patch is ... need something similar done to the OCL file too.
&#10;--- config/FindOrocos-RTT.cmake    2009-08-19 21:03:31.000000000 -0400&#10;+++ ../connectionNaming/FindOrocos-RTT.cmake    2009-07-21  &#10;21:18:50.000000000 -0400&#10;@@ -81,7 +81,7 @@&#10;#  Check version number&#10;#  user&#039;s &quot;1&quot; is passed as &quot;1.0.0&quot;&#10;#  user&#039;s &quot;1.4&quot; is passed as &quot;1.4.0&quot;&#10;-if ( ${OROCOS-RTT_VERSION} VERSION_LESS ${Orocos-RTT_FIND_VERSION})&#10;+if ( ${OROCOS-RTT_VERSION} LESS ${Orocos-RTT_FIND_VERSION})&#10;   MESSAGE(SEND_ERROR &quot;rtt-config.h reports version ${OROCOS- &#10;RTT_VERSION} &lt; required version ${Orocos-RTT_FIND_VERSION}&quot;)&#10;endif()&#10;&#10;

Examples, tutorials and help

On Thu, Aug 20, 2009 at 03:36, Stephen Roderick<kiwi [dot] net [..] ...> wrote:
> On Jul 22, 2009, at 08:55 , Peter Soetens wrote:
>
>> On Wed, Jul 22, 2009 at 13:41, Stephen Roderick<kiwi [dot] net [..] ...> wrote:
>>>
>>> On Jul 22, 2009, at 05:39 , Peter Soetens wrote:
>>>
>>>> On Wed, Jul 22, 2009 at 04:41, <kiwi [dot] net [..] ...> wrote:
>>>>>
>>>>> I have put another example up, this one concentrating on what I
>>>>> consider
>>>>> to be Orocos' best, most undocumented feature. That of naming
>>>>> connections,
>>>>> not ports, when deploying components. Incredibly useful, and not
>>>>> documented
>>>>> anywhere ... :-(
>>>>>
>>>>>
>>>>>
>>>>> http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-ak...
>>>>>
>>>>> When the website accepts .bz2 files, I will upload all files required.
>>>>
>>>> Done. Your (and every other Orocos developer's) upload limit is 10MB
>>>> in total and 1MB per file.
>>>
>>> Fantastic, thanks Peter. I've uploaded buildable tarballs for both
>>> examples.
>>>
>>> So ... any chance we can add .cpf to the list of accepted extensions?
>>> (and
>>> probably .osd and .ops as well, to round out the typical names for Orocos
>>> data files).
>>
>> I added .cpf back then as well, .osd and ops is now present too.
>>
>> Peter
>
> LOL ... this is from the FindOrocos-RTT.cmake file in the quicky project.
>
> &#10;&gt; -- Looking for RTT version v1.6.0&#10;&gt; CMake Error at config/FindOrocos-RTT.cmake:85 (MESSAGE):&#10;&gt;  rtt-config.h reports version 1.10.99 &lt; required version 1.6.0&#10;&gt; Call Stack (most recent call first):&#10;&gt;  CMakeLists.txt:17 (find_package)&#10;&gt;
>
> Patch is ... need something similar done to the OCL file too.
> &#10;&gt; --- config/FindOrocos-RTT.cmake 2009-08-19 21:03:31.000000000 -0400&#10;&gt; +++ ../connectionNaming/FindOrocos-RTT.cmake    2009-07-21&#10;&gt; 21:18:50.000000000 -0400&#10;&gt; @@ -81,7 +81,7 @@&#10;&gt; #  Check version number&#10;&gt; #  user&#039;s &quot;1&quot; is passed as &quot;1.0.0&quot;&#10;&gt; #  user&#039;s &quot;1.4&quot; is passed as &quot;1.4.0&quot;&#10;&gt; -if ( ${OROCOS-RTT_VERSION} VERSION_LESS ${Orocos-RTT_FIND_VERSION})&#10;&gt; +if ( ${OROCOS-RTT_VERSION} LESS ${Orocos-RTT_FIND_VERSION})&#10;&gt;  MESSAGE(SEND_ERROR &quot;rtt-config.h reports version ${OROCOS-RTT_VERSION} &lt;&#10;&gt; required version ${Orocos-RTT_FIND_VERSION}&quot;)&#10;&gt; endif()&#10;&gt;&#10;&gt;

You inverted the patch... but I got the point. We can probably remove
this check because enforce_version() is called later on which does the
check more correctly.

I had a discussion with Ruben yesterday on how to fix the whole
FindOrocosRTT.cmake file. We're going to use the 'config' mode of the
find_package macro and install the find file in
/usr/share/orocos-rtt/cmake/ (or equivalent on different platforms).
The file will be generated similar to a .pc file and contain all the
necessary includes/libraries of your installation hardcoded.

He's doing it now for KDL, although the .cmake file still depends on
pkg-config, but the concept seems to work.

Peter

Examples, tutorials and help

On Aug 20, 2009, at 08:47 , Peter Soetens wrote:

> On Thu, Aug 20, 2009 at 03:36, Stephen Roderick<kiwi [dot] net [..] ...>
> wrote:
>> On Jul 22, 2009, at 08:55 , Peter Soetens wrote:
>>
>>> On Wed, Jul 22, 2009 at 13:41, Stephen Roderick<kiwi [dot] net [..] ...>
>>> wrote:
>>>>
>>>> On Jul 22, 2009, at 05:39 , Peter Soetens wrote:
>>>>
>>>>> On Wed, Jul 22, 2009 at 04:41, <kiwi [dot] net [..] ...> wrote:
>>>>>>
>>>>>> I have put another example up, this one concentrating on what I
>>>>>> consider
>>>>>> to be Orocos' best, most undocumented feature. That of naming
>>>>>> connections,
>>>>>> not ports, when deploying components. Incredibly useful, and not
>>>>>> documented
>>>>>> anywhere ... :-(
>>>>>>
>>>>>>
>>>>>>
>>>>>> http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-ak...
>>>>>>
>>>>>> When the website accepts .bz2 files, I will upload all files
>>>>>> required.
>>>>>
>>>>> Done. Your (and every other Orocos developer's) upload limit is
>>>>> 10MB
>>>>> in total and 1MB per file.
>>>>
>>>> Fantastic, thanks Peter. I've uploaded buildable tarballs for both
>>>> examples.
>>>>
>>>> So ... any chance we can add .cpf to the list of accepted
>>>> extensions?
>>>> (and
>>>> probably .osd and .ops as well, to round out the typical names
>>>> for Orocos
>>>> data files).
>>>
>>> I added .cpf back then as well, .osd and ops is now present too.
>>>
>>> Peter
>>
>> LOL ... this is from the FindOrocos-RTT.cmake file in the quicky
>> project.
>>
>> &#10;&gt;&gt; -- Looking for RTT version v1.6.0&#10;&gt;&gt; CMake Error at config/FindOrocos-RTT.cmake:85 (MESSAGE):&#10;&gt;&gt;  rtt-config.h reports version 1.10.99 &lt; required version 1.6.0&#10;&gt;&gt; Call Stack (most recent call first):&#10;&gt;&gt;  CMakeLists.txt:17 (find_package)&#10;&gt;&gt;
>>
>> Patch is ... need something similar done to the OCL file too.
>> &#10;&gt;&gt; --- config/FindOrocos-RTT.cmake 2009-08-19 21:03:31.000000000 -0400&#10;&gt;&gt; +++ ../connectionNaming/FindOrocos-RTT.cmake    2009-07-21&#10;&gt;&gt; 21:18:50.000000000 -0400&#10;&gt;&gt; @@ -81,7 +81,7 @@&#10;&gt;&gt; #  Check version number&#10;&gt;&gt; #  user&#039;s &quot;1&quot; is passed as &quot;1.0.0&quot;&#10;&gt;&gt; #  user&#039;s &quot;1.4&quot; is passed as &quot;1.4.0&quot;&#10;&gt;&gt; -if ( ${OROCOS-RTT_VERSION} VERSION_LESS ${Orocos-RTT_FIND_VERSION})&#10;&gt;&gt; +if ( ${OROCOS-RTT_VERSION} LESS ${Orocos-RTT_FIND_VERSION})&#10;&gt;&gt;  MESSAGE(SEND_ERROR &quot;rtt-config.h reports version ${OROCOS- &#10;&gt;&gt; RTT_VERSION} &lt;&#10;&gt;&gt; required version ${Orocos-RTT_FIND_VERSION}&quot;)&#10;&gt;&gt; endif()&#10;&gt;&gt;&#10;&gt;&gt;
>
> You inverted the patch... but I got the point. We can probably remove
> this check because enforce_version() is called later on which does the
> check more correctly.

Agreed, we could rework some of this.

> I had a discussion with Ruben yesterday on how to fix the whole
> FindOrocosRTT.cmake file. We're going to use the 'config' mode of the
> find_package macro and install the find file in
> /usr/share/orocos-rtt/cmake/ (or equivalent on different platforms).
> The file will be generated similar to a .pc file and contain all the
> necessary includes/libraries of your installation hardcoded.

So we're depending on CMake's own config file support, now? Does that
mean we will be dropping support for pkgconfig files at some point?
Does CMake fully support this on all of our targetted platforms?

> He's doing it now for KDL, although the .cmake file still depends on
> pkg-config, but the concept seems to work.

Would love to see what is required on both the developer and user
fronts here.

Once we get this sorted out, I think we should put the FindOrocos-
RTT.cmake, etc, files under version control. We should make these
available to users, and will need to track changes to them. They don't
have to support all possible features, but IMHO should support
building component libraries and executables using Orocos. This is the
first task a user faces. No need to make everyone repeat it. Thoughts?

Stephen

Ruben Smits's picture

Examples, tutorials and help

On Fri, Aug 21, 2009 at 3:43 AM, Stephen Roderick<kiwi [dot] net [..] ...> wrote:
> On Aug 20, 2009, at 08:47 , Peter Soetens wrote:
>
>> On Thu, Aug 20, 2009 at 03:36, Stephen Roderick<kiwi [dot] net [..] ...>
>> wrote:
>>> On Jul 22, 2009, at 08:55 , Peter Soetens wrote:
>>>
>>>> On Wed, Jul 22, 2009 at 13:41, Stephen Roderick<kiwi [dot] net [..] ...>
>>>> wrote:
>>>>>
>>>>> On Jul 22, 2009, at 05:39 , Peter Soetens wrote:
>>>>>
>>>>>> On Wed, Jul 22, 2009 at 04:41, <kiwi [dot] net [..] ...> wrote:
>>>>>>>
>>>>>>> I have put another example up, this one concentrating on what I
>>>>>>> consider
>>>>>>> to be Orocos' best, most undocumented feature. That of naming
>>>>>>> connections,
>>>>>>> not ports, when deploying components. Incredibly useful, and not
>>>>>>> documented
>>>>>>> anywhere ... :-(
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-ak...
>>>>>>>
>>>>>>> When the website accepts .bz2 files, I will upload all files
>>>>>>> required.
>>>>>>
>>>>>> Done. Your (and every other Orocos developer's) upload limit is
>>>>>> 10MB
>>>>>> in total and 1MB per file.
>>>>>
>>>>> Fantastic, thanks Peter. I've uploaded buildable tarballs for both
>>>>> examples.
>>>>>
>>>>> So ... any chance we can add .cpf to the list of accepted
>>>>> extensions?
>>>>> (and
>>>>> probably .osd and .ops as well, to round out the typical names
>>>>> for Orocos
>>>>> data files).
>>>>
>>>> I added .cpf back then as well, .osd and ops is now present too.
>>>>
>>>> Peter
>>>
>>> LOL ... this is from the FindOrocos-RTT.cmake file in the quicky
>>> project.
>>>
>>> &#10;&gt;&gt;&gt; -- Looking for RTT version v1.6.0&#10;&gt;&gt;&gt; CMake Error at config/FindOrocos-RTT.cmake:85 (MESSAGE):&#10;&gt;&gt;&gt;  rtt-config.h reports version 1.10.99 &lt; required version 1.6.0&#10;&gt;&gt;&gt; Call Stack (most recent call first):&#10;&gt;&gt;&gt;  CMakeLists.txt:17 (find_package)&#10;&gt;&gt;&gt;
>>>
>>> Patch is ... need something similar done to the OCL file too.
>>> &#10;&gt;&gt;&gt; --- config/FindOrocos-RTT.cmake 2009-08-19 21:03:31.000000000 -0400&#10;&gt;&gt;&gt; +++ ../connectionNaming/FindOrocos-RTT.cmake    2009-07-21&#10;&gt;&gt;&gt; 21:18:50.000000000 -0400&#10;&gt;&gt;&gt; @@ -81,7 +81,7 @@&#10;&gt;&gt;&gt; #  Check version number&#10;&gt;&gt;&gt; #  user&#039;s &quot;1&quot; is passed as &quot;1.0.0&quot;&#10;&gt;&gt;&gt; #  user&#039;s &quot;1.4&quot; is passed as &quot;1.4.0&quot;&#10;&gt;&gt;&gt; -if ( ${OROCOS-RTT_VERSION} VERSION_LESS ${Orocos-RTT_FIND_VERSION})&#10;&gt;&gt;&gt; +if ( ${OROCOS-RTT_VERSION} LESS ${Orocos-RTT_FIND_VERSION})&#10;&gt;&gt;&gt;  MESSAGE(SEND_ERROR &quot;rtt-config.h reports version ${OROCOS-&#10;&gt;&gt;&gt; RTT_VERSION} &lt;&#10;&gt;&gt;&gt; required version ${Orocos-RTT_FIND_VERSION}&quot;)&#10;&gt;&gt;&gt; endif()&#10;&gt;&gt;&gt;&#10;&gt;&gt;&gt;
>>
>> You inverted the patch... but I got the point. We can probably remove
>> this check because enforce_version() is called later on which does the
>> check more correctly.
>
> Agreed, we could rework some of this.
>
>> I had a discussion with Ruben yesterday on how to fix the whole
>> FindOrocosRTT.cmake file. We're going to use the 'config' mode of the
>> find_package macro and install the find file in
>> /usr/share/orocos-rtt/cmake/ (or equivalent on different platforms).
>> The file will be generated similar to a .pc file and contain all the
>> necessary includes/libraries of your installation hardcoded.
>
> So we're depending on CMake's own config file support, now? Does that
> mean we will be dropping support for pkgconfig files at some point?
> Does CMake fully support this on all of our targetted platforms?

I don't know if we should drop pkgconfig, I have actually no idea how
many users actually use it.

>> He's doing it now for KDL, although the .cmake file still depends on
>> pkg-config, but the concept seems to work.
>
> Would love to see what is required on both the developer and user
> fronts here.

On the user side this should result in only using the find_package()
cmake function for orocos-xxx and not needing a FindOrocos-XXX.cmake
file anymore in every project that uses orocos-xxx.

On the develepor side we need to create this file so it will set all
needed variables for the find_package() function.

Ruben

> Once we get this sorted out, I think we should put the FindOrocos-
> RTT.cmake, etc, files under version control. We should make these
> available to users, and will need to track changes to them. They don't
> have to support all possible features, but IMHO should support
> building component libraries and executables using Orocos. This is the
> first task a user faces. No need to make everyone repeat it. Thoughts?
>
> Stephen
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

Examples, tutorials and help

On Aug 21, 2009, at 03:23 , Ruben Smits wrote:

> On Fri, Aug 21, 2009 at 3:43 AM, Stephen Roderick<kiwi [dot] net [..] ...>
> wrote:
>> On Aug 20, 2009, at 08:47 , Peter Soetens wrote:
>>
>>> On Thu, Aug 20, 2009 at 03:36, Stephen Roderick<kiwi [dot] net [..] ...>
>>> wrote:
>>>> On Jul 22, 2009, at 08:55 , Peter Soetens wrote:
>>>>
>>>>> On Wed, Jul 22, 2009 at 13:41, Stephen Roderick<kiwi [dot] net [..] ...>
>>>>> wrote:
>>>>>>
>>>>>> On Jul 22, 2009, at 05:39 , Peter Soetens wrote:
>>>>>>
>>>>>>> On Wed, Jul 22, 2009 at 04:41, <kiwi [dot] net [..] ...> wrote:
>>>>>>>>
>>>>>>>> I have put another example up, this one concentrating on what I
>>>>>>>> consider
>>>>>>>> to be Orocos' best, most undocumented feature. That of naming
>>>>>>>> connections,
>>>>>>>> not ports, when deploying components. Incredibly useful, and
>>>>>>>> not
>>>>>>>> documented
>>>>>>>> anywhere ... :-(
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-ak...
>>>>>>>>
>>>>>>>> When the website accepts .bz2 files, I will upload all files
>>>>>>>> required.
>>>>>>>
>>>>>>> Done. Your (and every other Orocos developer's) upload limit is
>>>>>>> 10MB
>>>>>>> in total and 1MB per file.
>>>>>>
>>>>>> Fantastic, thanks Peter. I've uploaded buildable tarballs for
>>>>>> both
>>>>>> examples.
>>>>>>
>>>>>> So ... any chance we can add .cpf to the list of accepted
>>>>>> extensions?
>>>>>> (and
>>>>>> probably .osd and .ops as well, to round out the typical names
>>>>>> for Orocos
>>>>>> data files).
>>>>>
>>>>> I added .cpf back then as well, .osd and ops is now present too.
>>>>>
>>>>> Peter
>>>>
>>>> LOL ... this is from the FindOrocos-RTT.cmake file in the quicky
>>>> project.
>>>>
>>>> &#10;&gt;&gt;&gt;&gt; -- Looking for RTT version v1.6.0&#10;&gt;&gt;&gt;&gt; CMake Error at config/FindOrocos-RTT.cmake:85 (MESSAGE):&#10;&gt;&gt;&gt;&gt;  rtt-config.h reports version 1.10.99 &lt; required version 1.6.0&#10;&gt;&gt;&gt;&gt; Call Stack (most recent call first):&#10;&gt;&gt;&gt;&gt;  CMakeLists.txt:17 (find_package)&#10;&gt;&gt;&gt;&gt;
>>>>
>>>> Patch is ... need something similar done to the OCL file too.
>>>> &#10;&gt;&gt;&gt;&gt; --- config/FindOrocos-RTT.cmake 2009-08-19 21:03:31.000000000 -0400&#10;&gt;&gt;&gt;&gt; +++ ../connectionNaming/FindOrocos-RTT.cmake    2009-07-21&#10;&gt;&gt;&gt;&gt; 21:18:50.000000000 -0400&#10;&gt;&gt;&gt;&gt; @@ -81,7 +81,7 @@&#10;&gt;&gt;&gt;&gt; #  Check version number&#10;&gt;&gt;&gt;&gt; #  user&#039;s &quot;1&quot; is passed as &quot;1.0.0&quot;&#10;&gt;&gt;&gt;&gt; #  user&#039;s &quot;1.4&quot; is passed as &quot;1.4.0&quot;&#10;&gt;&gt;&gt;&gt; -if ( ${OROCOS-RTT_VERSION} VERSION_LESS ${Orocos- &#10;&gt;&gt;&gt;&gt; RTT_FIND_VERSION})&#10;&gt;&gt;&gt;&gt; +if ( ${OROCOS-RTT_VERSION} LESS ${Orocos-RTT_FIND_VERSION})&#10;&gt;&gt;&gt;&gt;  MESSAGE(SEND_ERROR &quot;rtt-config.h reports version ${OROCOS-&#10;&gt;&gt;&gt;&gt; RTT_VERSION} &lt;&#10;&gt;&gt;&gt;&gt; required version ${Orocos-RTT_FIND_VERSION}&quot;)&#10;&gt;&gt;&gt;&gt; endif()&#10;&gt;&gt;&gt;&gt;&#10;&gt;&gt;&gt;&gt;
>>>
>>> You inverted the patch... but I got the point. We can probably
>>> remove
>>> this check because enforce_version() is called later on which does
>>> the
>>> check more correctly.
>>
>> Agreed, we could rework some of this.
>>
>>> I had a discussion with Ruben yesterday on how to fix the whole
>>> FindOrocosRTT.cmake file. We're going to use the 'config' mode of
>>> the
>>> find_package macro and install the find file in
>>> /usr/share/orocos-rtt/cmake/ (or equivalent on different platforms).
>>> The file will be generated similar to a .pc file and contain all the
>>> necessary includes/libraries of your installation hardcoded.
>>
>> So we're depending on CMake's own config file support, now? Does that
>> mean we will be dropping support for pkgconfig files at some point?
>> Does CMake fully support this on all of our targetted platforms?
>
> I don't know if we should drop pkgconfig, I have actually no idea how
> many users actually use it.

We use it. So you are proposing to support both pkgconfig and cmake-
config files?

>>> He's doing it now for KDL, although the .cmake file still depends on
>>> pkg-config, but the concept seems to work.
>>
>> Would love to see what is required on both the developer and user
>> fronts here.
>
> On the user side this should result in only using the find_package()
> cmake function for orocos-xxx and not needing a FindOrocos-XXX.cmake
> file anymore in every project that uses orocos-xxx.

Ok. So then the CREATE_COMPONENT() style macros in the existing
FindOrocos-RTT.cmake should be transferred to something separate, and
made available to end users I think.

> On the develepor side we need to create this file so it will set all
> needed variables for the find_package() function.

Ok. Is that about the same as making the pkgconfig file? Which I know
has mountains of issues with things like "libs.private". That field is
the bane of my existence! :-(
S

Examples, tutorials and help

On Fri, Aug 21, 2009 at 13:29, S Roderick<kiwi [dot] net [..] ...> wrote:
> On Aug 21, 2009, at 03:23 , Ruben Smits wrote:
>
>> On Fri, Aug 21, 2009 at 3:43 AM, Stephen Roderick<kiwi [dot] net [..] ...>
>> wrote:
>>> On Aug 20, 2009, at 08:47 , Peter Soetens wrote:
>>>
>>>> On Thu, Aug 20, 2009 at 03:36, Stephen Roderick<kiwi [dot] net [..] ...>
>>>> wrote:
>>>>> On Jul 22, 2009, at 08:55 , Peter Soetens wrote:
>>>>>
>>>>>> On Wed, Jul 22, 2009 at 13:41, Stephen Roderick<kiwi [dot] net [..] ...>
>>>>>> wrote:
>>>>>>>
>>>>>>> On Jul 22, 2009, at 05:39 , Peter Soetens wrote:
>>>>>>>
>>>>>>>> On Wed, Jul 22, 2009 at 04:41, <kiwi [dot] net [..] ...> wrote:
>>>>>>>>>
>>>>>>>>> I have put another example up, this one concentrating on what I
>>>>>>>>> consider
>>>>>>>>> to be Orocos' best, most undocumented feature. That of naming
>>>>>>>>> connections,
>>>>>>>>> not ports, when deploying components. Incredibly useful, and
>>>>>>>>> not
>>>>>>>>> documented
>>>>>>>>> anywhere ... :-(
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-ak...
>>>>>>>>>
>>>>>>>>> When the website accepts .bz2 files, I will upload all files
>>>>>>>>> required.
>>>>>>>>
>>>>>>>> Done. Your (and every other Orocos developer's) upload limit is
>>>>>>>> 10MB
>>>>>>>> in total and 1MB per file.
>>>>>>>
>>>>>>> Fantastic, thanks Peter. I've uploaded buildable tarballs for
>>>>>>> both
>>>>>>> examples.
>>>>>>>
>>>>>>> So ... any chance we can add .cpf to the list of accepted
>>>>>>> extensions?
>>>>>>> (and
>>>>>>> probably .osd and .ops as well, to round out the typical names
>>>>>>> for Orocos
>>>>>>> data files).
>>>>>>
>>>>>> I added .cpf back then as well, .osd and ops is now present too.
>>>>>>
>>>>>> Peter
>>>>>
>>>>> LOL ... this is from the FindOrocos-RTT.cmake file in the quicky
>>>>> project.
>>>>>
>>>>> &#10;&gt;&gt;&gt;&gt;&gt; -- Looking for RTT version v1.6.0&#10;&gt;&gt;&gt;&gt;&gt; CMake Error at config/FindOrocos-RTT.cmake:85 (MESSAGE):&#10;&gt;&gt;&gt;&gt;&gt;  rtt-config.h reports version 1.10.99 &lt; required version 1.6.0&#10;&gt;&gt;&gt;&gt;&gt; Call Stack (most recent call first):&#10;&gt;&gt;&gt;&gt;&gt;  CMakeLists.txt:17 (find_package)&#10;&gt;&gt;&gt;&gt;&gt;
>>>>>
>>>>> Patch is ... need something similar done to the OCL file too.
>>>>> &#10;&gt;&gt;&gt;&gt;&gt; --- config/FindOrocos-RTT.cmake 2009-08-19 21:03:31.000000000 -0400&#10;&gt;&gt;&gt;&gt;&gt; +++ ../connectionNaming/FindOrocos-RTT.cmake    2009-07-21&#10;&gt;&gt;&gt;&gt;&gt; 21:18:50.000000000 -0400&#10;&gt;&gt;&gt;&gt;&gt; @@ -81,7 +81,7 @@&#10;&gt;&gt;&gt;&gt;&gt; #  Check version number&#10;&gt;&gt;&gt;&gt;&gt; #  user&#039;s &quot;1&quot; is passed as &quot;1.0.0&quot;&#10;&gt;&gt;&gt;&gt;&gt; #  user&#039;s &quot;1.4&quot; is passed as &quot;1.4.0&quot;&#10;&gt;&gt;&gt;&gt;&gt; -if ( ${OROCOS-RTT_VERSION} VERSION_LESS ${Orocos-&#10;&gt;&gt;&gt;&gt;&gt; RTT_FIND_VERSION})&#10;&gt;&gt;&gt;&gt;&gt; +if ( ${OROCOS-RTT_VERSION} LESS ${Orocos-RTT_FIND_VERSION})&#10;&gt;&gt;&gt;&gt;&gt;  MESSAGE(SEND_ERROR &quot;rtt-config.h reports version ${OROCOS-&#10;&gt;&gt;&gt;&gt;&gt; RTT_VERSION} &lt;&#10;&gt;&gt;&gt;&gt;&gt; required version ${Orocos-RTT_FIND_VERSION}&quot;)&#10;&gt;&gt;&gt;&gt;&gt; endif()&#10;&gt;&gt;&gt;&gt;&gt;&#10;&gt;&gt;&gt;&gt;&gt;
>>>>
>>>> You inverted the patch... but I got the point. We can probably
>>>> remove
>>>> this check because enforce_version() is called later on which does
>>>> the
>>>> check more correctly.
>>>
>>> Agreed, we could rework some of this.
>>>
>>>> I had a discussion with Ruben yesterday on how to fix the whole
>>>> FindOrocosRTT.cmake file. We're going to use the 'config' mode of
>>>> the
>>>> find_package macro and install the find file in
>>>> /usr/share/orocos-rtt/cmake/ (or equivalent on different platforms).
>>>> The file will be generated similar to a .pc file and contain all the
>>>> necessary includes/libraries of your installation hardcoded.
>>>
>>> So we're depending on CMake's own config file support, now? Does that
>>> mean we will be dropping support for pkgconfig files at some point?
>>> Does CMake fully support this on all of our targetted platforms?
>>
>> I don't know if we should drop pkgconfig, I have actually no idea how
>> many users actually use it.
>
> We use it. So you are proposing to support both pkgconfig and cmake-
> config files?

Yes. There's no pain in keeping the pkgconfig files. They require
exact same info as the cmake-config files.

>
>>>> He's doing it now for KDL, although the .cmake file still depends on
>>>> pkg-config, but the concept seems to work.
>>>
>>> Would love to see what is required on both the developer and user
>>> fronts here.
>>
>> On the user side this should result in only using the find_package()
>> cmake function for orocos-xxx and not needing a FindOrocos-XXX.cmake
>> file anymore in every project that uses orocos-xxx.
>
> Ok. So then the CREATE_COMPONENT() style macros in the existing
> FindOrocos-RTT.cmake should be transferred to something separate, and
> made available to end users I think.

Ack.

>
>> On the develepor side we need to create this file so it will set all
>> needed variables for the find_package() function.
>
> Ok. Is that about the same as making the pkgconfig file? Which I know
> has mountains of issues with things like "libs.private". That field is
> the bane of my existence! :-(

I'm sure we'll learn tons of new stuff :-]

Peter

Examples, tutorials and help

On Jul 22, 2009, at 08:55 , Peter Soetens wrote:

> On Wed, Jul 22, 2009 at 13:41, Stephen Roderick<kiwi [dot] net [..] ...>
> wrote:
>> On Jul 22, 2009, at 05:39 , Peter Soetens wrote:
>>
>>> On Wed, Jul 22, 2009 at 04:41, <kiwi [dot] net [..] ...> wrote:
>>>>
>>>> I have put another example up, this one concentrating on what I
>>>> consider
>>>> to be Orocos' best, most undocumented feature. That of naming
>>>> connections,
>>>> not ports, when deploying components. Incredibly useful, and not
>>>> documented
>>>> anywhere ... :-(
>>>>
>>>>
>>>> http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-ak...
>>>>
>>>> When the website accepts .bz2 files, I will upload all files
>>>> required.
>>>
>>> Done. Your (and every other Orocos developer's) upload limit is 10MB
>>> in total and 1MB per file.
>>
>> Fantastic, thanks Peter. I've uploaded buildable tarballs for both
>> examples.
>>
>> So ... any chance we can add .cpf to the list of accepted
>> extensions? (and
>> probably .osd and .ops as well, to round out the typical names for
>> Orocos
>> data files).
>
> I added .cpf back then as well, .osd and ops is now present too.

And we missed .idl. Possible to add that too?
S

help

Hello,
I'm trying to install the kdl-1.0.0 lib. But I can't do the 'CMAKE'.
When I type the 'cmake' command the following error appears:

bert@pythia:~/Desktop/kdl-1.0.0/build$ cmake .
Orocos KDL version (1.0.0)
Build type set to 'RTT' by user.
CMake Error at config/FindEigen2.cmake:6 (MESSAGE):
-- Looking for Eigen2 - not found
Call Stack (most recent call first):
CMakeLists.txt:57 (INCLUDE)

-- Configuring done

But I'm sure I installed the Eigen2 lib.
Can you help me?

Thanks
Bert

_________________________________________________________________
Nieuws, entertainment en de laatste roddels. Je vind het op MSN.nl!
http://nl.msn.com/

help

On Aug 5, 2009, at 08:04 , Bert Godon wrote:

> Hello,
> I'm trying to install the kdl-1.0.0 lib. But I can't do the 'CMAKE'.
> When I type the 'cmake' command the following error appears:
>
> bert@pythia:~/Desktop/kdl-1.0.0/build$ cmake .
> Orocos KDL version (1.0.0)
> Build type set to 'RTT' by user.
> CMake Error at config/FindEigen2.cmake:6 (MESSAGE):
> -- Looking for Eigen2 - not found
> Call Stack (most recent call first):
> CMakeLists.txt:57 (INCLUDE)
>
>
> -- Configuring done
>
> But I'm sure I installed the Eigen2 lib.
> Can you help me?
>
> Thanks
> Bert

Please provide more information. What operating system and version?
Did you install Eigen in a package manager, or from source?
Stephen

help

Bert Godon wrote:
> Hello,
> I'm trying to install the kdl-1.0.0 lib. But I can't do the 'CMAKE'.
> When I type the 'cmake' command the following error appears:
>
> /bert@pythia:~/Desktop/kdl-1.0.0/build$ cmake .
> Orocos KDL version (1.0.0)
> Build type set to 'RTT' by user.
> CMake Error at config/FindEigen2.cmake:6 (MESSAGE):
> -- Looking for Eigen2 - not found
> Call Stack (most recent call first):
> CMakeLists.txt:57 (INCLUDE)
>
>
> -- Configuring done
> /
> But I'm sure I installed the Eigen2 lib.
> Can you help me?
>
> Thanks
> Bert
>
> Deel je favoriete foto's online met Windows Live Photos
> <http://www.microsoft.com/netherlands/windowslive/Views/productDetail.aspx?product=Photos>
Hi, the system is looking for includes on /usr/local/include and you
probably get it installed on /usr/local/include.

Go to /usr/local/include and make a symbolic link named Eigen2 to
/usr/local/include/eigen2/Eigen (or any other name you have).

Breno

help

On Aug 5, 2009, at 08:31 , Breno wrote:

> Bert Godon wrote:
>> Hello,
>> I'm trying to install the kdl-1.0.0 lib. But I can't do the 'CMAKE'.
>> When I type the 'cmake' command the following error appears:
>>
>> /bert@pythia:~/Desktop/kdl-1.0.0/build$ cmake .
>> Orocos KDL version (1.0.0)
>> Build type set to 'RTT' by user.
>> CMake Error at config/FindEigen2.cmake:6 (MESSAGE):
>> -- Looking for Eigen2 - not found
>> Call Stack (most recent call first):
>> CMakeLists.txt:57 (INCLUDE)
>>
>>
>> -- Configuring done
>> /
>> But I'm sure I installed the Eigen2 lib.
>> Can you help me?
>>
>> Thanks
>> Bert
>>
>> Deel je favoriete foto's online met Windows Live Photos
>> <http://www.microsoft.com/netherlands/windowslive/Views/productDetail.aspx?product=Photos
>> >
> Hi, the system is looking for includes on /usr/local/include and you
> probably get it installed on /usr/local/include.
>
> Go to /usr/local/include and make a symbolic link named Eigen2 to
> /usr/local/include/eigen2/Eigen (or any other name you have).

You are probably better off setting CMAKE_PREFIX_PATH or
CMAKE_INCLUDE_PATH when calling CMake, than monkeying with /usr
directories. Try with "export CMAKE_PREFIX_PATH=/usr/local" and then
do cmake. If not, try "export CMAKE_INCLUDE_PATH=/usr/local/include/
eigen2".

In reality, there should be _no_ explicit paths in the cmake files.
This has been introduced into RTT and OCL (at least), but I don't
think KDL has followed along yet.

Stephen

Examples, tutorials and help

I have put another example up, this one concentrating on what I consider to be Orocos' best, most undocumented feature. That of naming connections, not ports, when deploying components. Incredibly useful, and not documented anywhere ... :-(

http://orocos.org/wiki/rtt/simple-examples/name-connections-not-ports-ak...

When the website accepts .bz2 files, I will upload all files required.

HTH
Stephen