Sebastian Ehlert
Sebastian Ehlert
Trying to build molassembler against Nauty 2.7.2 fails with ``` [21/81] Building CXX object src/CMakeFiles/molassembler_obj.dir/Molassembler/Graph/Canonicalization.cpp.o FAILED: src/CMakeFiles/molassembler_obj.dir/Molassembler/Graph/Canonicalization.cpp.o /home/abt-grimme/opt/conda/envs/gcc/bin/x86_64-conda-linux-gnu-c++ -DBOOST_ALL_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEIGEN_USE_BLAS -DEIGEN_USE_MKL_ALL -I/tmp1/ehlert/scine/molassembler/src -I/tmp1/ehlert/scine/molassembler/_build/src -I/software/intel/parallel_studio_xe_2019/compilers_and_libraries_2019.6.324/linux/mkl/include -I/tmp1/ehlert/scine/molassembler/_build/RingDecomposerLib/src/RingDecomposerLib -isystem /home/abt-grimme/opt/conda/envs/scine/include -isystem...
Setting `-DBUILD_SHARED_LIBS=ON` does only additionally build a shared library and not disable the static library build. Further, linking against the shared library leads to missing symbols for some reason. Is...
Trying to build molassembler currently fails for me due to errors in the tests: ``` + cmake -DCMAKE_AR=/home/conda/staged-recipes/build_artifacts/scine-molassembler_1656626094491/_build_env/bin/x86_64-conda-linux-gnu-ar -DCMAKE_CXX_COMPILER_AR=/home/conda/staged-recipes/build_artifacts/scine-molassembler_1656626094491/_build_env/bin/x86_64-conda-linux-gnu-gcc-ar -DCMAKE_C_COMPILER_AR=/home/conda/staged-recipes/build_artifacts/scine-molassembler_1656626094491/_build_env/bin/x86_64-conda-linux-gnu-gcc-ar -DCMAKE_RANLIB=/home/conda/staged-recipes/build_artifacts/scine-molassembler_1656626094491/_build_env/bin/x86_64-conda-linux-gnu-ranlib -DCMAKE_CXX_COMPILER_RANLIB=/home/conda/staged-recipes/build_artifacts/scine-molassembler_1656626094491/_build_env/bin/x86_64-conda-linux-gnu-gcc-ranlib -DCMAKE_C_COMPILER_RANLIB=/home/conda/staged-recipes/build_artifacts/scine-molassembler_1656626094491/_build_env/bin/x86_64-conda-linux-gnu-gcc-ranlib -DCMAKE_LINKER=/home/conda/staged-recipes/build_artifacts/scine-molassembler_1656626094491/_build_env/bin/x86_64-conda-linux-gnu-ld -DCMAKE_STRIP=/home/conda/staged-recipes/build_artifacts/scine-molassembler_1656626094491/_build_env/bin/x86_64-conda-linux-gnu-strip -DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM=NEVER -DCMAKE_FIND_ROOT_PATH_MODE_LIBRARY=ONLY -DCMAKE_FIND_ROOT_PATH_MODE_INCLUDE=ONLY '-DCMAKE_FIND_ROOT_PATH=/home/conda/staged-recipes/build_artifacts/scine-molassembler_1656626094491/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl;/home/conda/staged-recipes/build_artifacts/scine-molassembler_1656626094491/_build_env/x86_64-conda-linux-gnu/sysroot' -DCMAKE_INSTALL_PREFIX=/home/conda/staged-recipes/build_artifacts/scine-molassembler_1656626094491/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl...
Installed versions of [nauty 2.7.2](https://pallini.di.uniroma1.it/nauty27r2.tar.gz), [RingDecomposerLib 1.1.3](https://github.com/rareylab/RingDecomposerLib/releases/tag/v1.1.3_rdkit) and [nlohmann_json 3.10.5](https://github.com/nlohmann/json/releases/tag/v3.10.5) are currently ignored by the build system and instead the dependencies are fetched again. Is there a way to avoid...
OpenMP is probably one of the easiest non-fpm compatible dependency fpm could provide. OpenMP is usually shipped with the compiler. For the current scope of GCC we only have to...
*Tracking issue for the progress on the Sovereign Tech Fund (STF) supported project to enable registry support in fpm.* Add features to fpm to support the usage of a package...
Before we make *fpm* aware of the [fpm-registry](https://github.com/fortran-lang/fpm-registry), we should create a minimal working implementation for a local registry (this registry might even be built-in to simplify things a bit...
We use fpm 0.3.0 in the CI to bootstrap fpm. Does it make sense to keep the oldest supported version there or should we move this version to the latest...
Came up in #220. At some point we might have to determine which compiler is used with fpm, therefore I tried to collect some information on the various Fortran compilers...
Being able to access the current VCS revision in the manifest and pass it to the project as macro would be useful to identify exactly which revision was build or...