-
Notifications
You must be signed in to change notification settings - Fork 130
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
Fortran interface in separate repository #301
Comments
So what you want is to be able to build the Fortran interface by linking it to an existing installation of the C libraries? |
Yes. I want to build the fortran interface, then link to an installation of sundials. |
This could also be achieved with adjustments to the CMakelists.txt files |
I think adjustments to the CMake would be the way to go. I have marked this as a feature-request. |
The Sundials CMake system looks complicated. I would try to submit a pull request but I think I would end up doing it in a way that would be satisfactory. Should I try or should I leave this to Sundials team? |
The CMake system is indeed a bit complicated. You can attempt it if you would like, and a contribution in this regard would be appreciated. I cannot promise that someone from the sundials team will be able to implement this in the near future. |
It would be useful if the Fortran interface was in a separate repository or if it could be built without building the C part of sundials.
I have a package that I'm putting on conda-forge (conda-forge/staged-recipes#23182 (comment)). It depends on sundials, but it requires the fortran interface. I can not link against the conda-forge sundials because it does not build the fortran interface. I need to instead, independent of conda-forge, build sundials with the fortran interface and link to my package.
Anyway, it would be useful to separate Sundials and the Fortran interface in some way.
The text was updated successfully, but these errors were encountered: