Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Build standalone Eclipse with CDT and custom plugins, command line

You asking how to build standalone eclipse product? Its not exactly question for cdt mailing list.
You can google on "how to build eclipse product". I suggest to use maven/tycho same as eclipse platform,
but could be other ways. The process is rather involved and cannot be answered in one email.
Check out this tutorial:

At some point of the process build system will product installation of the product, and you can zip it up and
ship as zip file or wrap in installer or linux packages and what not.

On Thu, Sep 5, 2019 at 12:14 PM Clément Hurlin <clement.hurlin@xxxxxxxxxxxxx> wrote:

Thank you Austin,

  I had checked out Oomph before and I believe it doesn't fit my use case (or I didn't understand how to do it). I don't want clients to have to launch oomph and choose our custom setup, it's a bit cumbersome (need to switch to oomph's "Advanced" mode); I want to provide them completely standalone Eclipse installs. But your answer prompted me to look again and I found my way using the p2 director application:

  With it I succeeded building a standalone Eclipse, installing the CDT using a public repo, and installing our own plugin specifying a file:/ URI for the update site!


ps: for reference, my command goes like this (highlighting our custom plugins):

./eclipse -application org.eclipse.equinox.p2.director -repository,file:/media/truecrypt1/pncide/releng/com.provenrun.pncide.tycho.updatesite/target/updatesite, -installIU org.eclipse.sdk.ide,, -destination /tmp/p2test/fromscratch/ -profile SDKProfile -profileProperties org.eclipse.update.install.features=true -bundlepool /tmp/p2test/fromscratch/ -p2.os linux -roaming

On Tue, Sep 03, 2019 at 06:38:27PM +0200, Clément Hurlin 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
 I believe you are looking for Oomph. This is a pretty decent write-up

Austin Morgan
cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top