> so you must first compile solution A, before solution B can be compiled This is the way how it works now (== the first of your two examples). The whole build is completely serialized till now. One process, no parallel builds.
Solution A emits a lib and a DLL, and solution B links against the resulting lib A to create another executable. Juts to give you some context: Our main goal when setting up CCNet is not so much a reduction of the build-time due to parallelisation (while that surely be a nice side effect), but a more convenient and controlled interaction with the SVN repository, specifically better control when a build should be triggered (i.e. some commits should trigger builds, while other commits should be ignored). Thanks for the time you invest to understand my setup.
