Christopher Pohl
|
Seperating the IDE / build project from the source tree
|
Christopher Pohl
06/14/2010 10:43 AM
post56752
|
Seperating the IDE / build project from the source tree
Dear all,
for a platform component which is built for multiple target architectures (not only QNX) we would like to organize the
source tree seperately from the build files and IDE project files, something like this:
project
+ build
+ container
+ <platofrm1>
+ <platform2>
+ <component1>
+ <platform1>
+ <platform2>
+ <component2>
+ <platform1>
+ <platform2>
+ [...]
+ src
+ <component1>
+ <component2>
The goal is to keep the source tree tidy and free of platform dependent description / build files.
The second goal is to share the project / build files via Subversion, thus all project / build files shall only
reference sources with relative paths such that the local working copy location is irrelevant.
We also want to be able to browse / edit / build / debug sources from the IDE of the repsective platform, e.g. QNX
Momentics. Thus, an IDE project located under the "build" tree should display associated sources from the "src" tree (e.
g. with an external sources link). It is acceptable that the external source location is disovered during the first
build (after SVN checkout) and the linked folder is only displayed afterwards.
Is it possible to set that up with the QNX Momentics IDE - without ending up with hardcoded paths in the IDE .project /
.cproject files ?
What project type (QNX C Project or Managed Project) is the better way to achieve it ?
Thanks,
Christopher
|
|
|