This cuts down on the number of CI jobs we run by first building the static library then building and running the tests with the static library, then building the shared library and dynamically linking the tests. We don't run the tests again in the interest of time. The shared library build was introduced in #48 to detect problems with the export definitions that only show up at link time in shared libraries on Windows. If the library and the tests build and link properly, then this issue should be caught.
Partially addresses #61
This cuts down on the number of CI jobs we run by first building the static library then building and running the tests with the static library, then building the shared library and dynamically linking the tests. We don't run the tests again in the interest of time. The shared library build was introduced in #48 to detect problems with the export definitions that only show up at link time in shared libraries on Windows. If the library and the tests build and link properly, then this issue should be caught.