Add note about GFortran usability to docs #302
Conversation
| @@ -4,6 +4,12 @@ Mounting UnifyCR | |||
|
|
|||
| In this section, we describe how to use the UnifyCR API in an application. | |||
|
|
|||
| .. Note:: **Fortran Compatibility** | |||
|
|
|||
| ``unifycr_mount`` and ``unifycr_unmount`` are now usable with GFortran. | |||
There was a problem hiding this comment.
Thanks @CamStan . Just because this looks strange to me, let's use the name in all lower case as "gfortran". That's how I see it most of the time.
There was a problem hiding this comment.
Well, seems to use lots of variants out on the web: "GFortran", "Gfortran", "gfortran", so I take that back. Good how you have it.
There was a problem hiding this comment.
Oh, we should mention that a Fortran application needs to link with:
-lunifycrf -lunifycr_gotcha
|
And let's mention that the Fortran source needs to include unifycrf.h: As an example for how to integrate the UNIFYCR_MOUNT/UNMOUNT calls, we could point users to: https://github.com/LLNL/UnifyCR/blob/dev/examples/src/writeread.f90 |
|
Updated. |
docs/build-intercept.rst
Outdated
| .. code-block:: Bash | ||
|
|
||
| $ mpif90 -o test_write test_write.F \ | ||
| -I<unifycr>/include -L<unifycy>/lib -lunifycrf -lunifycr_gotcha \ |
There was a problem hiding this comment.
@adammoody, I want to double check that this is correct.
There was a problem hiding this comment.
Aside from the extra \ on the end...
|
Nice! Thanks, @CamStan |
This adds a note about compatibility with GFortran to the docs and lets users know about issue #300.
This was accomplished with #288
Types of changes