Re: [Boost-build] How to stop propagate include paths of internal library

Subject: Re: [Boost-build] How to stop propagate include paths of internal library
From: Kevin Wheatley (hxpro_at_[hidden])
Date: 2009-03-17 06:19:08

Franz wrote:
> No not exactly. LibA needs to pass the LibA/inc to LibB because LibB includes
> header files form LibA/inc in its source files. So I think I need the
> usage-requirements. But I don't want that the LibA/inc is also passed to Exe
> because it only includes header files from LibB/inc.

If it only needs headers, then I typically create an 'alias' target to
refer to the includes only and refer to that as a source for the sub
library that way the dependency doesn't propagate beyond the sub
library build.

alias my_includes : : : : <include>include_dir ;

Kevin

-- 
| Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this      |
| Senior Technology                     | My employer for certain |
| And Network Systems Architect         | Not even myself         |