agrossfield
commented
10 months ago Bumping this. As far as I can tell, it's a 2-line change. Change recipe/build.sh to contain
cmake ${CMAKE_ARGS} \
-D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX=$PREFIX \
-D CMAKE_PREFIX_PATH=$PREFIX \
-D Python_EXECUTABLE=$PYTHON \
-D USE_PYTHON=ON \
-D CMAKE_CXX_VISIBILITY_PRESET=hidden \
-D CMAKE_VISIBILITY_INLINES_HIDDEN=ON \
-D CMAKE_INTERPROCEDURAL_OPTIMIZATION=ON \
-D BUILD_SHARED_LIBS=ON
.(the BUILD_SHARED_LIBS line is the new one).
Then, do the same thing to recipe/bld.bat (insert after line 8).
wojdyr
Solution to issue cannot be found in the documentation.
Issue
Related to Issue #57, as of now the package still only contains libgemmi.a and not libgemmi.so. In my hands, this breaks when I try to build my own conda-forge package (loos) on OS X, because the .a file isn't portable across compiler suites and the conda-forge runner uses a more recent compiler than you did to build it.
Someone commented in #57 that they're planning to turn on building the dynamic library by default and re-render the package. I'm just opening an issue to ensure it doesn't slip through the cracks.
Note: the conda list and conda info things aren't relevant, since the problem manifests in the GitHub build system too, which has a more minimal package list.
Installed packages
Environment info