-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default INSTALL path #69
Comments
All XACC plugins have to be installed to the original XACC install location (specifically, they get installed to ${XACC_ROOT}/plugins). Since TNQVM is a collection of XACC plugins, you can't specify a different CMAKE_INSTALL_PREFIX for TNQVM than that of your XACC build. It has to be installed to the original XACC install. If you want the TNQVM plugins to be installed to a different location, then you would have to install XACC to that location first. For that you can use CMAKE_INSTALL_PREFIX for your XACC build, and then ensure that downstream plugin builds pass -DXACC_DIR=NEW_XACC_INSTALL_LOCATION |
@amccaskey Yes, that's how it used to work before. Yesterday on Rhea I provided -DXACC_DIR=location, but TNQVM install tried to install files into /usr/local/something, no idea where /usr/local came from. The only way I could fix it is to provide the CMAKE_INSTALL_PREFIX=XACC_DIR. That's why I was asking what could potentially affect the build system recently. |
I've seen this sometimes when the CMake Cache gets messed up. Let me know if it still happens after you delete your TNQVM build directory and re-run CMake. |
When building the latest commit from Sep 22, 2020, it tried to install itself in the default path of /usr/local/, instead of the one provided by -DXACC_DIR (-DCMAKE_INSTALL_PREFIX was necessary to correct this). Did something change in the build system that could cause this behavior? If not, this could be just a problem with the platform where I tried to install it.
The text was updated successfully, but these errors were encountered: