Experimental fpm build/test/install capability #758
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of changes
This PR
install.sh
for macOS, Linux, and Windows Subsystem for Linux.test/
subdirectory containing Garden unit tests thatfpm
can run.src/tests
totests/
to preventfpm
from building the CTest tests because of a build error due to duplicate module names.tests/
directory location.fpm
from compiling them.example/
subdirectory with simple demonstration programs that fpm can run.fpm.toml
in a new.gitignore
file to prevent naive uses offpm
. (fpm
builds work only after the new version ofinstall.sh
has been run and has copied the newfpm.toml
file to the top-level source directory.)Rationale for changes
The old
install.sh
script was large, complicated, difficult to maintain, and was written in an era before Homebrew was stable across macOS and Linux and long beforefpm
existed. The new installer first installs Homebrew if it's missing, then uses Homebrew to install all OpenCoarrays prerequisites, and finally builds OpenCoarrays withfpm
, which enables developers to (re)build OpenCoarrays from source without CMake.Additional info and certifications
This pull request (PR) is a:
I certify that
OpenCoarrays developer a chance to review my proposed code
be introduced)
Code coverage data