Dmitry Goncharov wrote:
There is a restriction that shared and static versions of libunit_test_framework are not interchangeable. This makes it difficult to ship unit tests since the author of a unit test cannot predict what type of libunit_test_framework (shared or static) the user has on their machine.
1. This subject is discussed in length. Boost.Test opted for portability in between platform, instead of interchangeability between static and shared libraries. This is not a restriction, this is feature ;) 2. Am I to understand that you are library developer who ships unit tests along with library? 3. If answer is yes, do you ship your own makefiles? if yes, you can enforce specific library there. 4. If not, you can use single header variant of UTF and do not depend on library at all. It's not like your users are going to build your test modules over and over. 5. Your last option if none of the above fits is to make notes in documentation ;) Gennadiy