Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization

I was successful in installing CDT into an Eclipse SDK via a script. I figured I'd shared the exact details for anyone else looking to do the same:

1. Unzip the Eclipse SDK archive to c:\
2. Unzip the CDT p2 archive to c:\temp\p2
3. Create and run the following cmd file within c:\eclipse

eclipsec ^
   -application org.eclipse.equinox.p2.director  ^
   -nosplash ^
   --launcher.suppressErrors ^
   -consoleLog ^
   -destination c:\eclipse ^
-installIU ",,,,,,,,,,,,,,,,," ^
   -repository file:/c:/temp/p2

Note that the -installIU parameter would vary based on what features you want installed. You can get the full list of IU's by running the same cmdline but with '-list' instead of an '-installIU ...' switch.


At 04:19 PM 8/3/2010, Andrew Overholt wrote:
* John Cortell <rat042@xxxxxxxxxxxxx> [2010-08-03 17:07]:
> My understanding is CDT distributions are now strictly p2 archives and
> thus require installation via the Update Manager. Anyone know how this
> could be done via a script?

Look on the Eclipse wiki for docs on the p2 director application.  This
can be used in scripts so you'd do something like:

- unzip SDK archive
- cd eclipse
- ./eclipse -application org.eclipse.equinox.p2.director <other flags
  giving it the CDT zip as a repository> -installIU org.eclipse.cdt.sdk
  (or whatever you want to install)

That'll install it into the Eclipse installation from where you're
running the director application.  You can also install into other
Eclipse installations but that's probably not what you want in this


cdt-dev mailing list

Back to the top