Richard Carver
|
Using mkbuild for automated builds?
|
Richard Carver
01/27/2010 10:44 AM
post46052
|
Using mkbuild for 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
|
|
|