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

configure/cmake #365

Open
henkela opened this issue Sep 18, 2020 · 3 comments
Open

configure/cmake #365

henkela opened this issue Sep 18, 2020 · 3 comments

Comments

@henkela
Copy link

henkela commented Sep 18, 2020

Hi,
do you consider using cmake or autotools/automake in the future again? This would make it easier to have build recipes with easybuild for instance. Otherwise, one would have to prepare patches or a config.mk writer.
Best regards,
Andreas

@emstoudenmire
Copy link
Contributor

Hi Andreas,
No plans to do this at the moment. We don't want to have cmake required as a dependency, so at most in the future we could support it as an optional way to do the build.

Could you please elaborate more on the need to prepare patches or making a config.mk writer? I'm don't follow the context regarding either of those.

Miles

@henkela
Copy link
Author

henkela commented Sep 20, 2020

Hi Miles,
thanks for your prompt reply.
Well, many cluster admins use software installation frameworks like Easybuild(https://github.com/easybuilders/easybuild) or Spark. Those frameworks wrap the usual configuremake, cmake, and so on, to be able to install software easily and reproduceable. That is to say, compiler-wise compile options are managed centrally as well and applied upon installation.
As I understood the installation of ITensor one has to modify config.mk to contain the paths to the software/compilers and the compile-opts. If I want to install ITensor with Easybuild I'd have to prepare at least one patch that takes care of modifying config.mk. I didn't check yet but it may be necessary to have more than one patch to take variations in compilers/numerical libraries into account as well.
Best regards
Andreas

1 similar comment
@henkela
Copy link
Author

henkela commented Sep 20, 2020

Hi Miles,
thanks for your prompt reply.
Well, many cluster admins use software installation frameworks like Easybuild(https://github.com/easybuilders/easybuild) or Spark. Those frameworks wrap the usual configuremake, cmake, and so on, to be able to install software easily and reproduceable. That is to say, compiler-wise compile options are managed centrally as well and applied upon installation.
As I understood the installation of ITensor one has to modify config.mk to contain the paths to the software/compilers and the compile-opts. If I want to install ITensor with Easybuild I'd have to prepare at least one patch that takes care of modifying config.mk. I didn't check yet but it may be necessary to have more than one patch to take variations in compilers/numerical libraries into account as well.
Best regards
Andreas

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