To automate the build and to keep dependencies calculated by CB an MS Visual Studio approach to targets is needed, i.e. the ability to specify input files ( it is what we have as sources, it's ok with CB ) and the ability to specify file names that the custom commands produce ( it is what should be added to CB ). I.e. a target can produce not just a library or an exe-file, but it can produce a .CPP and .H for example. ( e.g. BISON/FLEX tools which build a compiler program sources from language description files, and reswrap tool from FOX toolkit, which embeds graphics etc. data into program by generating byte arrays and producing .c and .h sources to be compiled with the main program )...