For more infomation about this bug, visit
Summary: Make OCL::HelloWorld available as a loadable component
Product: OCL
Version: 1.4.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Other
AssignedTo: orocos-dev [..] ...
ReportedBy: peter [dot] soetens [..] ...
CC: orocos-dev [..] ...
Estimated Hours: 0.0
Created an attachment (id=222)
--> (https://www.fmtc.be/bugzilla/orocos/attachment.cgi?id=222)
Creates liborocos-helloworld-
The helloworld component of OCL is only usable as a program in the OCL build
directory. It is not installed and is thus not of use for people using the
binary packages. We can adapt the sources such that both program and component
library are built and that the latter is installed. See patch.
PS: This need was already addressed in the component builders manual, which
uses the helloworld component as a walk-through.
[Bug 503] Make OCL::HelloWorld available as a loadable component
For more infomation about this bug, visit
Peter Soetens
<peter [dot] soetens [..] ...> changed:
What |Removed |Added
--------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #3 from Peter Soetens
<peter [dot] soetens [..] ...> 2008-02-05 10:11:18 ---
Patch applied on trunk/ocl.
$ svn ci -m"Fixes bug #503 Make OCL::HelloWorld available as a loadable
component."
Sending helloworld/CMakeLists.txt
Sending helloworld/HelloWorld.cpp
Transmitting file data ..
Committed revision 28905.
[Bug 503] Make OCL::HelloWorld available as a loadable component
For more infomation about this bug, visit
Peter Soetens
<peter [dot] soetens [..] ...> changed:
What |Removed |Added
--------------------------------------------------------------------------
Status|NEW |ASSIGNED
Target Milestone|--- |1.4.1
--- Comment #2 from Peter Soetens
<peter [dot] soetens [..] ...> 2008-01-25 13:50:56 ---
(In reply to comment #1)
> Patch seems ok, but from your code I don't know whether it is necessary to have
> the activity hardcoded _in_ the component in order to create and use the
> component in the component library (I would have expected this info in the
> deployers xml file), or is this just for convenience (and hence not really
> belongs in this patch ;-)?
the point of the HelloWorld component is that with minimal effort, a component
runs. This is a step-in component before users are burdened with XML files.
Peter
[Bug 503] Make OCL::HelloWorld available as a loadable component
For more infomation about this bug, visit
Klaas Gadeyne <klaas [dot] gadeyne [..] ...> changed:
What |Removed |Added
--------------------------------------------------------------------------
CC| |klaas [dot] gadeyne [..] ...
--- Comment #1 from Klaas Gadeyne <klaas [dot] gadeyne [..] ...> 2008-01-25 09:30:31 ---.so component library
(In reply to comment #0)
> Created an attachment (id=222)
--> (https://www.fmtc.be/bugzilla/orocos/attachment.cgi?id=222) [details]
> Creates liborocos-helloworld-
>
> The helloworld component of OCL is only usable as a program in the OCL build
> directory. It is not installed and is thus not of use for people using the
> binary packages. We can adapt the sources such that both program and component
> library are built and that the latter is installed. See patch.
Patch seems ok, but from your code I don't know whether it is necessary to have
the activity hardcoded _in_ the component in order to create and use the
component in the component library (I would have expected this info in the
deployers xml file), or is this just for convenience (and hence not really
belongs in this patch ;-)?
Klaas