Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] New Build Mechanism in Place

Hi Tracy,

There is one line in the build.xml file that unzips a regular eclipse SDK 
build which is specified with the eclipseZip property. I have it 
defaulting to a file which, for me, is a soft link to the 
latest integration build that I download. As well, the launches 
the build.xml file using a separate eclipse installation that I use to 
play in the org.eclipse.cdt.releng project (i.e. ../../eclipse)

To run the test target, you also need the org.eclipse.test and 
org.eclipse.ant.optional.junit plugins. I get these directly off of the 
/home/eclipse repository. So my workspace includes these plugins as well 
as the org.eclipse.cdt.releng project. I see I have unfortunately 
hardcoded the paths to these two plugins but it's probably easiest to 
check them out into the same workspace you check the cdt.releng plugin 

That's about all I do to get things going.  The scripts still aren't where 
I want them, though. For example, they always build off of HEAD as I just 
haven't had the time to integrate cvs tagging into the process yet. I'd 
certainly accept patches to the scripts as well :)

Having said all that, you could also use Eclipse's internal Export to 
deployable feature item to create a zip by hand. Or if you are working on 
patches, the gang here generally uses the Runtime Workbench, JUnit Plugin 
Test launch configurations to do our development and testing. The command 
line build is mainly for automated, i.e. hands off, builds.

Doug Schaefer, IBM's Eclipse CDT Architect
Ottawa (Palladium), Ontario, Canada

"Tracy Miranda" <TMIRANDA@xxxxxxxxxx> 
Sent by: cdt-dev-admin@xxxxxxxxxxx
04/20/2004 02:57 PM
Please respond to


RE: [cdt-dev] New Build Mechanism in Place


We'd like to get set up building CDT 2.0 and being able to run the tests
so we can be in a good position to submit patches. Can you give a few
tips on getting set-up to build CDT from command line...

I've had a look at the and can see the actual command to run +
how to  overwrite settings in build.xml. 
What I'm not clear about is:
- What other setup is involved, such as Eclipse plugins - should these
be unzipped somewhere, with version nos removed ?
- What (if anything besides the build scripts or releng plugin) do you
need checked out of cvs before you start ? 

Any tips to get me going will be much appreciated. 

Tracy Miranda
Altera Europe
Software R&D 

-----Original Message-----
From: Douglas Schaefer [mailto:dschaefe@xxxxxxxxxx] 
Sent: 10 March 2004 15:15
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] New Build Mechanism in Place

Hey all, 

Those who have tracked the nightly builds will notice some changes. The 
new build mechanism is now in place and is driving the nightly builds. 
Some things you'll see:
- Version numbers now have the timestamp of when the build started
of a build number.
- The platform specific features are gone and the base CDT feature is
the one you install (along with the builders).
- Zip files are generated. These are versioned without the timestamp
2.0.0). There is a zip for each platform and then one for each builder 
- The tests are now performed using Eclipse's test framework (again, we 
used to have this a long time ago)
- The 2.0 build page has the links to the test results as well as the
files (

For those who want to build the CDT themselves, I haven't had the chance

to write up a readme file yet. You can, however, take a look at the 
contents of org.eclipse.cdt.releng. Everything starts at the 
script which calls the build.xml ant file which then goes off into
other components including the PDE build scripts.

Doug Schaefer, Senior Software Developer
IBM Rational Software, Ottawa, Ontario, Canada
cdt-dev mailing list
cdt-dev mailing list

Back to the top