OCL 2.0 cleanup+removed lots of components

Submitted by peter on Fri, 2010-08-27 21:20

I'm about to push OCL 2.0 patches that remove all 'unmaintained' parts of OCL
and adapt OCL to the new cmake logic worked out by Adolfo, which has been
integrated in RTT master.

If you used any of the components in motion_control, hardware, cartesian,
vision, viewer, they are all gone. If you are interested in using these
components, you'll have to create a repository to maintain them. I'll probably
pick up some that are in hardware, but that's not high priority right now.

Peter

‹ 2.0 TaskBrowser and new types Compilation time regression due to boost::fusion ›
»

OCL 2.0 cleanup+removed lots of components

Submitted by snrkiwi on Fri, 2010-08-27 21:28.

On Aug 27, 2010, at 17:19 , Peter Soetens wrote:

> I'm about to push OCL 2.0 patches that remove all 'unmaintained' parts of OCL
> and adapt OCL to the new cmake logic worked out by Adolfo, which has been
> integrated in RTT master.
>
> If you used any of the components in motion_control, hardware, cartesian,
> vision, viewer, they are all gone. If you are interested in using these
> components, you'll have to create a repository to maintain them. I'll probably
> pick up some that are in hardware, but that's not high priority right now.

Ok, wow! What is left then?

I use items from hardware and motion_control, so some of those will definitely end up being maintained. Not sure about vision, we went our own way there.

So what is the goal of OCL now? Just deployer, taskbrowser, logging and helloworld?
S

»