On Wed, 10 Jul 2002, Erik Jaesler wrote: > >> make libcppunit.so". I was under the impression that jam built the > >> entire dependency tree regardless of where in the tree you were > >> building. That being the case, why doesn't jam "know how to make > >> libcppunit.so" when it's clearly in the tree? > > > >Your impression is unfortunately incorrect. The current Jam system can > >only build targets in the current directory or subdirectories. I > >critized this behavior as a side note on this list earlier. It can be > >fixed, but not without changing Jambase. > > Now that you remind me, I do remember you mentioning this. So let's fix > it! I know there's been some argument that we don't want to be using a > "custom" version of jam (like there are so many other BeOS projects out > there using jam that would be adversely effected), but this seems like a > pretty no-brainer modification to do, and will certainly make the tool > more useful. I don't think this issue is that pressing. Therefore I would rather see everything building first and then we can think about improving the situation. CU, Ingo