Martin Storsjö martin@martin.st writes:
For these cases, where a library is built as only a static library, one fairly common convention (not used everywhere, but at least in some libraries I regularly use) is to include the private dependencies in the non-private section. This makes sure a user of the library doesn't need to be concerned about which way this library was built (unless the user intentionally overrides defaults by passing flags such as -static to the linker).
Makes some sense to me. Is there any reasonable way to test these things? If not part of the ordinary make check, perhaps part of make distcheck or some other separate target.
If you feel like it, it would be nice with a short description of how it's intended to work, in the node "Linking" in the manual.
Regards, /Niels