Hi,
I'm using the cmake macros defined in UseOROCOS-RTT.cmake for my project and
have an own-made typekit. I know that there is the orocos_typekit() macro, but
that one only works with typegen. Apparently there is no other macro that will
put my typekit in the lib/orocos/typekit directory during build time.
I know I can use the orocos_component() macro and use the INSTALL option to
put it in a own-defined install directory but this is not an option for me
since I want to test stuff out before I install.
I'm willing to create a patch myself, therefor my question:
Is it better to adapt the orocos_typekit macro or create a new macro for this
use-case.
Ruben
UseOROCOS-RTT.cmake does not have a macro for own-made typekits
On Monday 22 November 2010 11:09:58 Ruben Smits wrote:
> Hi,
>
> I'm using the cmake macros defined in UseOROCOS-RTT.cmake for my project
> and have an own-made typekit. I know that there is the orocos_typekit()
> macro, but that one only works with typegen. Apparently there is no other
> macro that will put my typekit in the lib/orocos/typekit directory during
> build time.
>
> I know I can use the orocos_component() macro and use the INSTALL option to
> put it in a own-defined install directory but this is not an option for me
> since I want to test stuff out before I install.
>
> I'm willing to create a patch myself, therefor my question:
>
> Is it better to adapt the orocos_typekit macro or create a new macro for
> this use-case.
I already had a patch for this. I just pushed it to master.
I changed the macros to be:
orocos_typekit_headers( headers... )
# calls typegen (or should we call it orocos_typegen_headers(...) ???
orocos_typekit( typekitname files.cpp ) #builds a custom typekit
The latter also supports INSTALL incase you require it.
Peter
UseOROCOS-RTT.cmake does not have a macro for own-made typekits
On Monday 22 November 2010 11:48:19 Peter Soetens wrote:
> On Monday 22 November 2010 11:09:58 Ruben Smits wrote:
> > Hi,
> >
> > I'm using the cmake macros defined in UseOROCOS-RTT.cmake for my project
> > and have an own-made typekit. I know that there is the orocos_typekit()
> > macro, but that one only works with typegen. Apparently there is no other
> > macro that will put my typekit in the lib/orocos/typekit directory during
> > build time.
> >
> > I know I can use the orocos_component() macro and use the INSTALL option
> > to put it in a own-defined install directory but this is not an option
> > for me since I want to test stuff out before I install.
> >
> > I'm willing to create a patch myself, therefor my question:
> >
> > Is it better to adapt the orocos_typekit macro or create a new macro for
> > this use-case.
>
> I already had a patch for this. I just pushed it to master.
Note: master is still stabilizing so upgrading production code to master is
probably not a good idea. You'd better copy/paste the file or cherry-pick the
commit to your local branch.
Peter