Fix support for building static library with Visual Studio #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In PR #60, I tried to improve support for using docopt with Visual Studio when building/using the shared library
docopt.dll
. In doing so, I introduced a bug when trying to build/use docopt as a static library (docopt_s.lib
) in Visual Studio.Basically, I had been defining
DOCOPTAPI
to be__declspec(dllimport)
when building the static library. But when building a static library, neither__declspec(dllimport)
nor__declspec(dllexport)
should be used.This PR fixes the bug. The new behavior is as follows. When building the shared library, one must define both
DOCOPT_DLL
andDOCOPT_API
. When using the shared library, one must defineDOCOPT_DLL
. The user need not worry about these macros at all; they are handled by CMake. For example, a client project with the following CMakeLists.txt will causeDOCOPT_DLL
to automatically be defined when compilingfoo.cpp
.Locally, I tested both the shared library
docopt.dll
and the static librarydocopt_s.lib
with a small CMake client project.