Commit Graph

3 Commits

Author SHA1 Message Date
Greg Landrum
67f507a15c Some cmake cleanup work (#7720)
* cmake modernization

- get rid of some warnings
- switch to what I hope is the correct way of doing things
- bump min cmake version to 3.16
- bump min boost version to 1.70

This builds on linux

* remove some usages of PYTHON_EXECUTABLE

* remove old-school python usage from coverage tests

* remove unused CI file

* bump boost version for windows builds to 1.84

* still trying to get the ci builds working

* typo

* eventually the CI will work

* robustify some tests
2024-08-16 17:11:31 +02:00
Hussein Faara
7a9d807a48 Some Clang-specific build instructions skip some clang compilers on mac #6941 (#6942)
Updated compiler id comparisons to do a regex comparison against "Clang"
instead of doing a direct string comparison. This allows us to match
compiler ids like "AppleClang"
2023-11-29 17:25:36 +01:00
Brian Kelley
626f8b522d RDKit learns how to compute code coverage for tests
To use code coverage:

cmake -DCMAKE_BUILD_TYPE=Debug \
      -DRDK_USE_FLEXBISON=ON \
      -DRDK_TEST_COVERAGE=ON \
      <path to rdkit source tree>

make install
make RDKit_coverage

Note, when making RDKit_coverage, your python paths, (DY)LD_LIBRARY paths must be
set up correctly.  If any of the tests fail, the coverage generator will most
likely fail and certainly will not be complete.

Here is an example from my OSX Box (note, I set the install directory to rdkit_build via)
cmake -DCMAKE_INSTALL_PREFIX=`pwd`/rdkit_build \
    ...

RDBASE=<path to rdkit source>  DYLD_LIBRARY_PATH=`pwd`/rdkit_build/lib \
 PYTHONPATH=`pwd`/rdkit_build/lib/python2.7/site-packages \
 make RDKit_coverage

open coverage/index.html in a browser
2015-01-15 11:53:27 -05:00