>> 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. e Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves. -William Pitt, British prime-minister (1759-1806)