This PR implements an option to switch between building shared and static libraries. This is more or less the same I did in maeparser (https://github.com/schrodinger/maeparser/pull/57). Please note that this PR depends on the one in maeparser, and should not be merged before that one.
Added the COORDGEN_BUILD_SHARED_LIBS flag: ON == shared library, OFF == static. The required dependencies (boost, zlib), as well as the unit tests, will use the same linking type as specified by the flag. If maeparser needs to be built from source, it will also use the same linking type as indicated here.
In the tests: removed the BOOST_TEST_DYN_LINK macro.
Added some new Azure pipelines to build static libs. These have also been reformatted, looking like bigger changes that they actually are.
Please note that the Travis and appveyor builds do neither exercise the static builds.
As mentioned in the maeparser PR, I tested that, one these changes are live in maeparser and coordgen, RDKit and Openbabel won't break, and will still be able to build without any changes.
This PR implements an option to switch between building shared and static libraries. This is more or less the same I did in maeparser (https://github.com/schrodinger/maeparser/pull/57). Please note that this PR depends on the one in maeparser, and should not be merged before that one.
Added the
COORDGEN_BUILD_SHARED_LIBSflag:ON== shared library,OFF== static. The required dependencies (boost, zlib), as well as the unit tests, will use the same linking type as specified by the flag. If maeparser needs to be built from source, it will also use the same linking type as indicated here.In the tests: removed the
BOOST_TEST_DYN_LINKmacro.Added some new Azure pipelines to build static libs. These have also been reformatted, looking like bigger changes that they actually are.
These changes have also been tested in my CI builds (https://dev.azure.com/ricrogz/mycoordgen/_build/results?buildId=391).
Please note that the Travis and appveyor builds do neither exercise the static builds.
As mentioned in the maeparser PR, I tested that, one these changes are live in maeparser and coordgen, RDKit and Openbabel won't break, and will still be able to build without any changes.