Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Using mkbuild for the IDE to automated builds?: (3 Items)
   
Using mkbuild for the IDE to automated builds?  
We will use the Windows-based Hudson (http://hudson-ci.org/) application to perform the automated build process.

We use Clearcase for source code control and integrate it into the IDE.

We use Klocwork for static code analysis and also have it integrated into the IDE.

We would like to use mkbuild for automated builds so that the automated build uses the same environment and tools used 
by the IDE builds  (IDE is Version: 4.6.0 Build id: I20090510).

We were planning on using QNX C and QNX C++ Projects types for creating new projects from the IDE.

We are only using X86 "debug" and "release" build variants.

What files would we need to include in source control so that projects and workspaces build correctly for our automated 

builds?

For each project I believe the correct files (besides the actually source code files and headers) would be:

 .project
 .cproject
 .qnx_internal.mk
 common.mk
 Makefile
 x86\Makefile
 x86\o-g\Makefile
 x86\o\Makefile

Does that seem correct?


What about the Workspace files?

From the looks of it one of them might be:

 .metadata\.plugins\com.qnx.tools.ide.qde.core\qdeBuildInfo

Is that correct?  Are there any others that would need to be maintained under source control?


Thanks in advance!
Rich


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

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