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

Per-language compile options with FindESMF.cmake #20

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

Chrismarsh
Copy link
Contributor

If a custom Fortran compile options (ESMF_F90COMPILEOPTS) are provided, these are saved in the esmf.mk file that is read by FindESMF.cmake. If a C or C++ program is compiled using FindESMF.cmake, these non-compatible options are passed to the C++ compiler causing possible errors. This change ensures per-language options are set in the target.

This change is per ticket 3615070.

…mf.mk file that is read by FindESMF.cmake. If a C or C++ program is compiled using FindESMF.cmake, these non-compatible options are passed to the C++ compiler causing possible errors. This change ensures per-language options are set in the target.
@theurich
Copy link
Member

We need to add a C++ ESMF_HelloWorld.C and C ESMF_HelloWorld.c executable to the https://github.com/esmf-org/esmf-extended-tests/tree/develop/ESMF_HelloWorld_CMake. Then make sure our current FindESMF.cmake works for Fortran, C++, and C applications.
In particular, test the condition when a user sets explicit custom compile options, as per the comment by user.

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

Successfully merging this pull request may close these issues.

2 participants