Skip to content
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

Is conda installation available for qe-gipaw? #14

Open
tsitsvero opened this issue Dec 5, 2022 · 2 comments
Open

Is conda installation available for qe-gipaw? #14

tsitsvero opened this issue Dec 5, 2022 · 2 comments

Comments

@tsitsvero
Copy link

Is conda installation available for qe-gipaw?

It seems gipaw.x is not included with default qe conda installation...

@dceresoli
Copy link
Owner

The compilation of qe-gipaw could be activated in the QE conda recipe. I've seen they use cmake, and I need to test building gipaw with cmake. If it will work, I will contact the QE conda recipe author.

@tsitsvero
Copy link
Author

tsitsvero commented Dec 7, 2022

Great, thanks!

I tried to modify the conda recipe to compile qe with gipaw flags:

cmake .. \
    -DQE_ENABLE_MPI=ON \
    -DQE_ENABLE_OPENMP=ON \
    -DQE_ENABLE_SCALAPACK=ON \
    -DQE_ENABLE_ELPA=ON \
    -DQE_ENABLE_HDF5=ON \
    -DQE_ENABLE_TEST=ON \
    -DCMAKE_INSTALL_PREFIX=${PREFIX} \
    -DMPIEXEC_PREFLAGS="--oversubscribe;--bind-to;none;-mca;plm;isolated" \
    -DMPIEXEC_MAX_NUMPROCS=2  \
    -DTESTCODE_NPROCS=2 \
    -DQE_ENABLE_FOX=ON \
    -DQE_ENABLE_PLUGINS="gipaw"

It compiles okay, and executable gipaw.x is produced.

The fork for conda recipe is here: I have to change url (now points to the original repo within receipt since previous link to archive at github was old, and didn't contain proper link to qe-gipaw).

The annoying thing is that this executable isn't copied by make install for some reason to the /bin/ directory of the final conda package.

I suspect that some install target should be added at the side of qe within CMakeLists.txt

Is there anything to be changed at qe-gipaw side to make the gipaw.x file copied by make install or is it necessary to update something on their side?

As a workaround probably I can just copy the gipaw.x manually within build.sh script, but this corrupts the proper installation process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants