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

Use unique Fortran module names #511

Merged
merged 2 commits into from
Aug 3, 2024
Merged

Use unique Fortran module names #511

merged 2 commits into from
Aug 3, 2024

Conversation

mmuetzel
Copy link
Contributor

@mmuetzel mmuetzel commented Aug 2, 2024

Some CMake generators (e.g., Ninja) require that Fortran modules have unique names. That is because these generators create .mod files for these modules in a common folder (fmodules in the build tree).

Two files in fem/tests define Fortran modules named ToroidCurrents. Append numbers to these module names to work around the issue with some CMake generators (like Ninja).

Fixes #491.

Also, use Ninja on Windows now that it works.

Some CMake generators (e.g., Ninja) require that Fortran modules have
unique names. That is because these generators create `.mod` files for
these modules in a common folder (`fmodules` in the build tree).

Two files in `fem/tests` define Fortran modules named `ToroidCurrents`.
Append numbers to these module names to work around the issue with some
CMake generators (like Ninja).

Fixes ElmerCSC#491.
The default generator of CMake on MSYS2 is Ninja. It performs better than
the "MSYS Makefiles" generator on Windows (because `ninja` is a native
application on Windows unlike `make`).

Use it after ElmerCSC#491 is fixed.
@raback raback merged commit feabc69 into ElmerCSC:devel Aug 3, 2024
5 of 6 checks passed
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.

Build fails due to conflicting ToroidCurrents module definitions
2 participants