Definitely working on a clean folder with the latest AmberTools. Though I
did find this:
The file it's amber20_src/build/cmake_install.cmake and it's created by the
*run_cmake* script. If I backup that file:
mv cmake_install.cmake backup_cmake_install.cmake
and run the *run_cmake* script again (so the *build* folder is not clean),
I get a new cmake_install.cmake, different from the previous one in those
exact 116-118 lines:
if("x${CMAKE_INSTALL_COMPONENT}x" STREQUAL "xPythonx" OR NOT
CMAKE_INSTALL_COMPONENT)
execute_process(COMMAND /usr/bin/cmake -E create_symlink
$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/miniconda/bin/pip
$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/bin/amber.pip)
endif()
If I start all over again, moving AmberTools21.tar.bz2 to a new clean
folder, and running the *run_cmake* script inside the *build* folder, then
I get the same old cmake_install.cmake script, with the same 116-118 lines,
creating that symlink.
Could it be, then, that you're not starting from a fresh folder? :P
Here're the cmake scripts. I'm pasting them in plain text since I don't
know if this list supports gmails link embedding:
old backed up cmake_install.cmake:
https://www.dropbox.com/s/tpxn4c1ulccjetr/backup_cmake_install.cmake?dl=0
new cmake_install.cmake:
https://www.dropbox.com/s/7lb6uzzb0q4vnlp/cmake_install.cmake?dl=0
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Fri Oct 15 2021 - 13:00:03 PDT
