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

Support Octopus 14.0 #103

Open
fangohr opened this issue Mar 13, 2024 · 3 comments
Open

Support Octopus 14.0 #103

fangohr opened this issue Mar 13, 2024 · 3 comments
Assignees
Labels
p:high high priority

Comments

@fangohr
Copy link
Owner

fangohr commented Mar 13, 2024

  • add checksum and version for 14.0
  • check it compiles fine
  • once successful, put in merge request upstream in spack
@lang-m
Copy link
Collaborator

lang-m commented Mar 13, 2024

Do we want to switch to CMake for 14? According to the MRs listed in the release notes CUDA should (?) work.

@fangohr
Copy link
Owner Author

fangohr commented Mar 13, 2024

Do we want to switch to CMake for 14? According to the MRs listed in the release notes CUDA should (?) work.
I would propose a two-step approach:

  1. make Octopus 14 available via spack, keeping autotools as the built utility. The main advantage here is that this should be a fast fix. That's what I had in mind for this issue.

  2. make it possible to build octopus 14 with Cmake in Spack. This is the future, so it needs to happen, but it may be non-trivial, and take some time. (That's why I wanted to address point 1. first). I will create a second ticket for the CMake transition.

Is this a reasonable approach @lang-m , @iamashwin99 ?

@fangohr fangohr added the p:high high priority label Mar 13, 2024
@fangohr
Copy link
Owner Author

fangohr commented Mar 13, 2024

I have created the additional issue #104 for point 2.

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

No branches or pull requests

3 participants