[Boost-build] Advice on a good way to handle exported headers?

From: Daniel Einspanjer (deinspanjer_at_[hidden])
Date: 2006-03-05 11:23:40

In our current makefile world, each makefile has a list of headers to be 
exported.  make rules copy these listed headers to LOCAL/include 
directories.

I honestly don't like this system much, and I'd prefer to have explicit 
include folders created by the developer with the desired headers actually 
living in that folder in CVS.

Unfortunately, I need to finish the port to BB before I can make the 
secondary argument of changing all our source tree to adopt this new 
standard.

Currently, for the purposes of porting, I am just ignoring the issue by 
doing a:
project : usage-requirements <include>. ;

Which means there is no separation between externally available headers and 
internal ones.

Does anyone have any advice on a way I could accommodate this need for 
explicit export lists without changing our source tree structure?
-- 
Daniel Einspanjer