Re: [cdt-dev] Build standalone Eclipse with CDT and custom plugins, comm

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

Hi  Clément,

The product file is not much more than a list of plug-ins or features, by wrapping it in a pom.xml you can build your product from the command line using maven.

I recommend you look at the C/C++ Product and use that as a starting point. This is in the Eclipse EPP project (src code's README), (specifically the .product file is of interest). You may be able to draw inspiration from the GNU MCU project. It has a fork of EPP and does I recommend (adding the GNU MCU plug-ins in that case to the .product file). You can even include the product file and associated machinery in your main repo and only have to do a single build.

The alternative is to script something around the p2 director command line tools. For example, you can do something like this to add a feature to an eclipse install at the command line:

./eclipse/eclipse -application org.eclipse.equinox.p2.director -consoleLog -noSplash \
    -repository https://site/my/p2/dir \
    -installIUs org.my.feature.id.feature.group

HTH,

Jonah

 

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com

On Tue, 3 Sep 2019 at 12:38, Clément Hurlin <clement.hurlin@xxxxxxxxxxxxx> wrote:

Dear CDT developers,

  A few months ago I requested guidance from regarding generating .cproject files from the command line. This project is now deployed internally and users are happily generating CDT configurations (from a web service backed up by command line) specifically tuned for the products we develop at Prove&Run \o/

  I'm writing to you again because we would now like to send complete installations of Eclipse, including the CDT as well as a few custom plugins; to customers so that they are gently introduced to the code we ship to them. However, I don't understand how to do that. I know how to build standalone Eclipse using tycho by using .product files. But this mechanism requires to have a product to point to. In my case I don't have a product, simply a list of RCP plugins (or features, which we use to build standalone update sites).

  In other words I'd like to build a vanilla installation of the CDT augmented with our custom plugins; exactly as if I had taken a vanilla installation and manually installed our plugins from an update site. Do you have any pointer on how to do that from the command line?

Best regards,

Thanks for your hard work on the CDT,

Clément Hurlin

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev