On Wed, Jul 26, 2017 at 12:16 AM, Peter Dimov via Boost
Niall Douglas wrote:
The implication is that when a library changes from header-only to > static/shared, all dependent libraries need to change themselves to > static/shared too.
I'm not sure if this is a question or a statement. But in either case, yes it does.
My point was that under my overcomplicated scheme, this doesn't happen. Your dependency may change from header-only to static/shared, or from static/shared to header-only, and you don't need to do anything.
And when I say "change" here, I mean that version 1 was header-only, version 2 becomes static/shared, version 3 becomes header-only again, and dependents don't need to make corresponding changes each time this occurs.
Isn't this automatic in Niall's scheme too? I don't know but it should be. -- Olaf