Replies: 1 comment 1 reply
-
Hi @gclimon, At compile time (i.e. when you compile CESM with neural-fortran or any other Fortran library with modules as a dependency), you need to provide the path to the compiled modules in the include path ( At link time, you only need to pass the compiled library files ( I don't have experience with CESM but I've built other similar models many times and they're all similar but somewhat different. Can you provide your build log and the error messages that you get when you try to use neural-fortran from CESM? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Every example here I've found uses this as a module, rather than a linked library, which does not build/link correctly with the CESM (https://escomp.github.io/CESM/versions/cesm2.1/html/) model I'm currently trying to use this with. However, it is my understanding that the point of building this library on my system is that I would be able to just link to it (the lib{}.a files in /neural-fortran-main/build/lib/) and not need the explicit 'use' statements that imply it being used solely as a compiled module. Has anybody had any luck with this and could share an example or guidance? When I link the library files to my CESM build as an external library, it is identified, yet calling the internal functions does not work.
Beta Was this translation helpful? Give feedback.
All reactions