Dynamic library definitions

[gulachek]

Boost uses a pattern to have a macro that should be included only when using dynamic library. Do we need to add something like "dynamic definitions"? Current alternatives are that consumer defines macros if using dynamic library or we make a separate, for example, org.boost.log.dll library with the definitions. I like the former better as the latter would force dealing with workaround libraries down the road if we support this.

[gulachek]

Now dynamic/static libraries are separate libraries