RE: Importing cs-studio into eclipse

[Richard Fearn <Richard.Fearn@esss.se>]

Hi,

> My bad for not mentioning that I have read the pdf. And I did clone and
> import https://github.com/ControlSystemStudio/maven-osgi-bundles.git and
> https://github.com/ControlSystemStudio/cs-studio-thirdparty.git as well.

That shouldn't be necessary if you just want to work on the CS-Studio code. The bundles in those two (p2) repos can be used as they are.

> Although I did not clone and import org.csstudio.product.git. I did not
> mention it because I was in a state of total confusion (which I have to
> admit is my usual state whenever I try to build cs-studio).

You should be able to build the CS-Studio 'core' plugins and features, and the 'applications' plugins and features, without this repo. But you'll need it in order to take those plugins/features and create a standalone CS-Studio product.

> I must also admit that I always have tones and tones of errors when I
> import all the plugins into eclipse (3.2.x and eariler).

I would use a newer version of Eclipse - i.e. Luna/4.4 - as that's what CS-Studio is based on these days.

Also it isn't strictly necessary to import *all* the plugins into Eclipse - only those for which you actually want to work on the source code.

> Because there is no way to tell exactly which
> plugins you actually need (and of course those plugins will require other
> plugins, and so on) and it’s too slow to import all the plugins one by
> one.

This seems to be a big weakness using Tycho/Maven compared to using Buckminster for Eclipse development. Buckminster allows you to say "I want to get X into my workspace" and it will automatically import X and all of its dependencies, potentially from multiple git repositories and multiple p2 repositories.

That said, Andrej Babic at Cosylab wrote an Eclipse plugin to assist with this (specifically for CS-Studio). You can find it here:

  https://github.com/ControlSystemStudio/com.cosylab.css.importer

It will import a CS-Studio plugin, including its dependencies.

> So I usually import them all and ignore the errors. With this new
> maven build on master, I have to import all the plugins anyway. Then I end
> up with thousands of errors. Does anyone else have this problem or is it
> just me?

Not just you :-)

Regards,

Richard

--

Richard Fearn
richard.fearn@esss.se