I often confirm that CMake will build Amber without build errors. But I've
not had time to do much testing of the resulting executables.
Jamie now has a -DINSTALL_TESTS=TRUE option which will put the test
cases into the install directory. There is no top-level Makefile (in
$AMBERHOME), but you can run tests in the usual way in $AMBERHOME/test
and $AMBERHOME/AmberTools/test.
Is anyone doing this? I get tons of failures on macos (esp. with NAB and
cpptraj). I've spent sometime debugging, but I think they are related to the
fact that CMake builds dynamic libraries everywhere, whereas the conventional
Make scripts use mostly static libraries (except where dynamic is required,
as with python).
On Linux, things are generally better (for AT), but I still get 18 failures
that I don't see with the regular make system.
So: is anyone running tests using CMake? (We really need to install the
$AMBERHOME/Makefile to simplify this process.) Does it seem to work better
than for me? Anyone looking for something to do is welcome to try to get this
better tested. I fear that we may have to continue to support two parallel
build systems for a while, but I'd sure like to push the transition to CMake
as soon as we can.
...thx...dac
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Sat Jan 20 2018 - 08:00:02 PST
