If you design your project directories as cb, than there is no problem. I think that is the reason you
don't know about the problem?
I build other project too ;)
Take, for example, the rendering engine OGRE. I 've built this using CB. Here is a rough directory structure:
ogrenew <-- top dir
Build <-- I created this dir to put all build files in
OgreMain
include
src <-- main DLL source dir
scripts <-- project files for VC. This is where OgreMain.cbp resides ;)
... <-- more directories with other DLLs source files
In the CB project, I have two targets: Debug and Release. These are the build dirs defined for those targets:
Debug objects: ..\..\Build\Debug
Debug deps: ..\..\Build\.deps
Release objects: ..\..\Build\Release
Release deps: ..\..\Build\.deps
Let me note here that all relative paths in CB are relative to the project file (.cbp)
When I build OgreMain.cbp (the Release target), the Build directory has the following structure:
ogrenew <-- top dir
Build <-- I created this dir to put all build files in
Release <-- this is the main build dir for the Release target
OgreMain
src <-- this dir is filled with object files
OgreMain
include
src <-- main DLL source dir
scripts <-- project files for VC. This is where OgreMain.cbp resides ;)
... <-- more directories with other DLLs source files
Do you see something wrong with the above?
I don't ;)
Something just came to my mind: I always use the "direct-mode" for building, i.e. no GNU make. Maybe there is a bug there? I 'll have to check.
Have you tried building your project using "direct-mode"? Are your results the same?
Yiannis.