Description Maneesh Mehra 2005-03-14 15:43:54 EST

Hi:

I am trying to create a startup CDT project for the entire team (that will
be checked-in in our source VOBs). I would like to include symbolic
references to all the needed sources in this project. The need for this
project is quite simple. When a new person comes along, they will create
their own project and refer this project in their Project's reference list.

The problem that I am trying to solve is centered around specifying build
targets for this shared project.We have a very different building mechanism.
We use clearcase all throughout and use clearmake for our builds. We have
smart makefile(s) in each folder that we build. By smart build files I mean
that our build files dynamically build the list of folders that are needed
to be built. In addition, clearmake makes sure that it does not have to
build things unecessarily and is able to wink-in derived objects from the
VOB. Each folder in our source VOB contains a copy of this makefile. Assume
that the folder hierarchy is like:

folder1
    makefile
    folder2
        makefile
        folder3
            makefile

With our makefiles, if we issue a command like "clearmake -f makefile
PASS_MAKE_INCLUDES" in folder2, it builds files in folder2 only and not in
folder1 or folder3. Also, the build command names themselves are common
across the board for all folders. So PASS_MAKE_INCLUDES only builds the
include files for a given folder. Likewise, PASS_MAKE_LIBRARIES builds only
the libraries in a given folder. So, I would like to specify a build target
just once at the top level (i.e., folder1 in this case) and want it to
cascade down to all folders underneath folder1. However, in CDT, I would
have to specify the same build targets again and again for each folder in
the hierarchy. Is there a way so that build targets can be specified at the
project level ? This will also help any new folders inherit the
project-level build targets and will help us the pain of making sure that
they are being built correctly.