Christian Damus(deleted)
|
Re: Using mkbuild for the IDE to automated builds?
|
Christian Damus(deleted)
01/27/2010 11:22 AM
post46064
|
Re: Using mkbuild for the IDE to automated builds?
Hi, Richard,
Ah! I just replied on the other forum. Here, for the benefit of this
audience, is my earlier reply:
--------8<--------
The mkbuild script is intended to be used with an IDE workspace and
requires an IDE installation on your build machine.
The workspace contains an enormous amount of cache data in
the .metadata/ directory that you don't want to maintain in ClearCase.
What you will need to do on the build machine is:
- launch the IDE to create a new workspace
- add all of the projects that you need to build to the workspace (use
the
"Import Existing Projects" wizard for this)
- in the "Window -> Preferences" dialog, the "General / Workspace"
page,
check the "Refresh Automatically" option. Because you will checkout
the projects before the build, replacing their contents, this should
ensure that the IDE finds changes to makefiles, .cproject settings,
etc.
In your build script, make sure that your ClearCase checkout replaces
the projects in their original location on the filesystem.
-------->8--------
HTH,
Christian
|
|
|
Bryan Hansen
|
Re: Using mkbuild for the IDE to automated builds?
|
Bryan Hansen
07/09/2010 4:48 PM
post59117
|
Re: Using mkbuild for the IDE to automated builds?
Hi Richard,
I'm working on implementing a similar automated build system for our project. We're building for x86 debug and release
and also using Klocwork for static analysis.
I'm curious how this system worked out for you. Were you able to use Hudson to create a suitable environment? Did you
version control any or all of the eclipse metadata to avoid having to set up the eclipse workspace before performing a
build?
I'd appreciate any tips, tricks and advice you may have.
Thanks,
Bryan
|
|
|