Re: Creating support-only libs with orocreate-pkg

Hi Charles,

On Thu, Nov 29, 2012 at 11:03 AM, Charles Lesire-Cabaniols
<[email protected]> wrote:
> Hi devs,
>
> I would like to use the orocreate-pkg macro to create empty packages with
> only support libraries (i.e., no Orocos component nor typekit inside).
>
> When doing 'orocreate-pkg myLib support', I have several issues; only the
> first one is blocking IMO:
> 1. the library name in the CMake file is "support", meaning that all support
> libs will have the same name! I think "myLib", or "myLib-support" would be
> better!
> 2. the CMake file and the manifest.xml file add a dependency to 'rtt' that
> is not needed for 'support-only' packages

I agree...

>
> Actually, none of this points are blocking ME ;)
> I just would like my "users" to do an 'orocreate-pkg myLib support', modify
> almost only the 'src' folder, and then 'amake myLib' to compile and
> install...
>
> Rock has a very nice tool in that sense: rock-create-lib.
> It also helps filling the manifest.xml file, and even ask for dependencies!
>
> Would it be possible to port that tool to the orocos-toolchain also?
> I would like to avoid creating a dependency to Rock.base only for that
> tool...

It's certainly something we could accept. I don't think such a script
would necessarily depend on Rock.base. Having orocreate-pkg part of
ocl is equally misplaced...

Peter
-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev