Age | Commit message (Collapse) | Author |
|
|
|
|
|
Workaround for compiler bug when building Windows release.
Update M_CLI2 revision to include same fix.
|
|
|
|
|
|
|
|
|
|
- describe complete bootstapping process in collapsed details section
|
|
Lowercase openmp pragmas
|
|
Remove white-space changes from compiler branch for PR
|
|
|
|
added called *--fc* that sets the Fortran compiler name.
+ The default compiler name to use is taken from the value of the
environment variable FPM_FC.
+ If not set, the environment variable FC is used.
+ If it is not set the name _gfortran_ is used.
+ The value specified on the command line overrides any default.
FC is apparently a commonly used environment variable for the compiler,
is short, and allows for specifying compilers for other languages like
C (ie. `-cc gcc`) That is part of the reasons to use `--fc` instead of
`--compiler`.
Since there is a chance the currently set value of FC may be used by
other applications being used, and to allow for a temporary change of
the default the fpm-specific variable FPM_FC is supported in addition
to FC and has higher precedence.
However, since the Haskell version has a similar switch called
**--compiler** that name is an alias for **-fc**.
A skeleton was started for standard debug and release builds that allows
for compilers other than **gfortran**. I now have access to **ifort**
and **nvfortran** and it works with at least simple cases for those
compilers. Looking for someone with access to other compilers to help
flesh that out.
The list of executables to run with the `run` and `test` subcommands
can now be prefixed with **--target**, as with the Haskell version of
ffpm(1).
So default usage is unchanged from the previous version. By simply setting
FC or FPM_FC you can use it like the previous version with other compilers for
default debug and release builds.
How does that sound?
wget http://www.urbanjost.altervista.org/REMOVE/ffpm.f90
gfortran ffpm.f90 -o $HOME/.local/bin/ffpm
```
# get a test package or use your own
if [ ! -d M_CLI2 ]
then
git clone https://github.com/urbanjost/M_CLI2
fi
cd M_CLI2
# default build using ifort
ffpm build --fc ifort
export FPM_FC=ifort
ffpm run
ffpm test
|
|
CI: upload binaries when a release is published
|
|
Add --runner option to Fortran fpm to match Haskell fpm
|
|
|
|
|
|
Refactoring of manifest types
|
|
|
|
Move enumeration of link target object dependencies out of backend and into fpm_targets module.
Add string_cat function for concatenating arrays of string_t.
Add comments and procedure descriptions.
|
|
|
|
|
|
Separate build targets into schedule regions for parallel builds.
|
|
|
|
|
|
|
|
|
|
|
|
- move defaults from fpm to fpm_manifest
- rename all manifest types from *_t to *_config_t
- instance names correspond to table names in manifest
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fix docs CI failing #240
|
|
I didn't found any `set-env` command in the JamesIves repo, so maybe bumping the version fixes the issue.
|
|
Test and executable runner options
|
|
|
|
for the user to interact directly with the build/ directory, which ideally
should be a black box as far as the user is concerned.
--runner CMD A command to prefix the program execution paths with.
For use with utilities like valgrind(1), time(1), and
other utilities that launch executables; commands that
inspect the files like ldd(1), file(1), and ls(1); and
that copy or change the files like strip(1) and install(1).
EXAMPLES
# install executables in directory (assuming install(1) exists)
fpm run -c 'install -b -m 0711 -p -t /usr/local/bin'
|