26 Aug
2017
26 Aug
'17
8:55 a.m.
2017-08-25 10:12 GMT+00:00 Andrey Semashev via Boost
If the API is required by the library, I can see two solutions:
1. Make the API selection mandatory for users and act accordingly to the user's choice in headers. I.e., as Gavin suggested, test the macros and error out on unsupported combination.
I'll take this solution for header-only version of the library.
2. Move that part of the code to a compiled library and define the necessary macros for that library in the Jamfile or .cpp files. The public headers become neutral to the selected API in this case.
And this solution for the compiled llibrary version. Thanks for the suggestions, patches will be applied soon! -- Best regards, Antony Polukhin