20 Oct
2018
20 Oct
'18
9:52 p.m.
Steven Watanabe wrote:
That seems a bit worrisome to me, as I really don't like the idea of having a mixed-state sytem in the long term. It'll be really easy to end up with targets that use both the global /boost/headers and the library specific include paths. I can live with that as a temporary measure, but it's still ugly.
This is unavoidable - in the interim or otherwise - unless we either somehow solve, or outright eliminate, cyclic dependencies. Until then, libraries that form a cycle have to remain /boost//headers.