orocreate-pkg component package generator script

Here's an update on my efforts to create this orocreate-pkg script

You can invoke it with:
$ ocl/scripts/pkg/orocreate-pkg foo
or (after 'make install' of ocl):
$ orocreate-pkg foo

Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
build/install step, installs stuff like this (so only relevant
if you use 'make install') :

<pre>
installdir/
|-- include
| `-- orocos
| `-- foo
| |-- foo-component.hpp
| |-- transports
| | |-- corba
| | | |-- Convertions.hpp
| | | |-- fooTypesC.h
| | | |-- fooTypes.idl
| | | `-- TransportPlugin.hpp
| | `-- mqueue
| | `-- TransportPlugin.hpp
| |-- typekit
| | `-- Plugin.hpp
| |-- types
| | `-- foo
| | `-- foo-types.hpp
| `-- Types.hpp
|-- lib
| |-- orocos
| | |-- foo
| | | |-- libfoo-gnulinux.so
| | | |-- manifest.xml
| | | `-- types
| | | |-- libfoo-transport-corba-gnulinux.so
| | | |-- libfoo-transport-mqueue-gnulinux.so
| | | |-- libfoo-transport-typelib-gnulinux.so
| | | `-- libfoo-typekit-gnulinux.so
| | `-- types
| `-- pkgconfig
| |-- foo-transport-corba-gnulinux.pc
| |-- foo-transport-mqueue-gnulinux.pc
| |-- foo-transport-typelib-gnulinux.pc
| |-- foo-typekit-gnulinux.pc
| `-- orocos-foo-gnulinux.pc
`-- share
`-- orogen
|-- foo.tlb
`-- foo.typelist
</pre>

Take a careful look at the install directories. every lib/header is under an
orocos/foo subdirectory. This deviates from default typegen, which installs
transports and typekits under lib/orocos.

You can then load the component in the deployer by saying:

import("foo"), given that '/installdir/lib/orocos' is in your
RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.

This import statement will find the subdirectory 'foo' and load all
components/transports/typekits under that directory.

This package generator should also be useful to the ROS users, so create valid
ros packages, and build them ros-style, but without refering to ros in the
CMakeLists.txt file directly. ROS detection could should go into the RTT's
UseOrocos-RTT.cmake file, this is currently there, but untested (It calls
rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I'll prepare a wiki page with basic instructions on how this tool should help.
If you want to test this you need latest toolchain-2.1 branch of
rtt/ocl/orogen.

Although I pushed this to stable branches (evil me), there's still room for
changes/discussion. I just put it there such that most users could test it
right away before there's a release.

Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter

Ruben Smits's picture

orocreate-pkg component package generator script

On Monday 18 October 2010 12:40:26 Peter Soetens wrote:
> Here's an update on my efforts to create this orocreate-pkg script
>
> You can invoke it with:
> $ ocl/scripts/pkg/orocreate-pkg foo
> or (after 'make install' of ocl):
> $ orocreate-pkg foo
>
> Which, creates CMake files, example .cpp/hpp/.pc/.xml files etc. After a
> build/install step, installs stuff like this (so only relevant
> if you use 'make install') :
>
> <pre>
> installdir/
>
> |-- include
> |
> | `-- orocos
> |
> | `-- foo
> |
> | |-- foo-component.hpp
> | |-- transports
> | |
> | | |-- corba
> | | |
> | | | |-- Convertions.hpp
> | | | |-- fooTypesC.h
> | | | |-- fooTypes.idl
> | | |
> | | | `-- TransportPlugin.hpp
> | |
> | | `-- mqueue
> | |
> | | `-- TransportPlugin.hpp
> | |
> | |-- typekit
> | |
> | | `-- Plugin.hpp
> | |
> | |-- types
> | |
> | | `-- foo
> | |
> | | `-- foo-types.hpp
> |
> | `-- Types.hpp
> |
> |-- lib
> |
> | |-- orocos
> | |
> | | |-- foo
> | | |
> | | | |-- libfoo-gnulinux.so
> | | | |-- manifest.xml
> | | |
> | | | `-- types
> | | |
> | | | |-- libfoo-transport-corba-gnulinux.so
> | | | |-- libfoo-transport-mqueue-gnulinux.so
> | | | |-- libfoo-transport-typelib-gnulinux.so
> | | |
> | | | `-- libfoo-typekit-gnulinux.so
> | |
> | | `-- types
> |
> | `-- pkgconfig
> |
> | |-- foo-transport-corba-gnulinux.pc
> | |-- foo-transport-mqueue-gnulinux.pc
> | |-- foo-transport-typelib-gnulinux.pc
> | |-- foo-typekit-gnulinux.pc
> |
> | `-- orocos-foo-gnulinux.pc
>
> `-- share
> `-- orogen
>
> |-- foo.tlb
>
> `-- foo.typelist
> </pre>
>
> Take a careful look at the install directories. every lib/header is under
> an orocos/foo subdirectory. This deviates from default typegen, which
> installs transports and typekits under lib/orocos.
>
> You can then load the component in the deployer by saying:
>
> import("foo"), given that '/installdir/lib/orocos' is in your
> RTT_COMPONENT_PATH. Use import("path/to/foo/lib/orocos") for ros packages.
>
> This import statement will find the subdirectory 'foo' and load all
> components/transports/typekits under that directory.
>
> This package generator should also be useful to the ROS users, so create
> valid ros packages, and build them ros-style, but without refering to ros
> in the CMakeLists.txt file directly. ROS detection could should go into
> the RTT's UseOrocos-RTT.cmake file, this is currently there, but untested
> (It calls rosbuild_init() and sets the LIBRARY_OUTPUT_PATH ros-style).

I can confirm that it is not working ;), I'm still figuring out why.

R.

> I'll prepare a wiki page with basic instructions on how this tool should
> help. If you want to test this you need latest toolchain-2.1 branch of
> rtt/ocl/orogen.
>
> Although I pushed this to stable branches (evil me), there's still room for
> changes/discussion. I just put it there such that most users could test it
> right away before there's a release.
>
> Peter