| Age | Commit message (Collapse) | Author |
|---|
|
- default is equal to debug unless --flag is present and overwrites all arguments
- debug is the developement profile, options given by --flag are appended
- release is the production profile, options given by --flag are appended
|
|
|
|
|
|
Minor fix: for setting executable link libraries.
|
|
Executable link libraries were not working when auto discovery was on.
|
|
Add Conda install instructions to the README
|
|
|
|
|
|
|
|
Add ford-compatible documentation to fpm_strings.f90
|
|
Co-authored-by: Laurence Kedward <laurence.kedward@bristol.ac.uk>
|
|
|
|
|
|
|
|
|
|
Separate build targets from model structure
|
|
|
|
|
|
|
|
Update: install script for Fortran fpm
|
|
Changed behavior for run subcommand per @LKedwards suggestions
|
|
Co-authored-by: Laurence Kedward <laurence.kedward@bristol.ac.uk>
|
|
Co-authored-by: Laurence Kedward <laurence.kedward@bristol.ac.uk>
|
|
|
|
|
|
|
|
Co-authored-by: Sebastian Ehlert <28669218+awvwgk@users.noreply.github.com>
|
|
finish ..
document
|
|
The default behavior becomes very similar to the Rust cargo(1)
package manager in that
# run application if there is one target
fpm run -- ARGS cargo run -- ARGS
fpm run NAME(S) cargo run --example NAME
fpm run --example NAME(S) cargo run --example NAME
fpm run --compiler CMP cargo --profile PROFILE-NAME
DIFFERENCES:
<-- fpm allows multiple names
<-- fpm does not have profiles, just compiler at this time
<-- fpm allows for quoted globbing strings which lets you
easily select all or groups by name substrings
<-- fpm lists available targets if an unknown name or no
name and multiple targets are available, or if special
name "." is specified. From the documentation I do not
see anything indicating if cargo(1) lists targets or
not.
So the common cases are very similiar, with extensions in fpm
to list and run groups of applications using a few special
globbing strings (just going from the cargo documentation; it
might behave differently).
|
|
close #371
|
|
|
|
Just a few documentation tweaks.
Since the documentation has to change for this PR anyway, cleaned up a few
dusty corners primarily for the "run" subcommand that needed updated to
reflect building now being the default for a run subcommand, for clarity,
and to reflect the auto-build abilitites not available.
|
|
|
|
|
|
|
|
Co-authored-by: Sebastian Ehlert <28669218+awvwgk@users.noreply.github.com>
|
|
Co-authored-by: Sebastian Ehlert <28669218+awvwgk@users.noreply.github.com>
|
|
Co-authored-by: Sebastian Ehlert <28669218+awvwgk@users.noreply.github.com>
|
|
|
|
--target NAME(s) list of specific application names to execute.
No name is required if only one application exists.
If no name is supplied and more than one candidate
exists or a name has no match a list is produced
and fpm(1) exits.
Simple "globbing" is supported where "?" represents
any single character and "*" represents any string.
Therefore a quoted asterisk '*' runs all programs.
|
|
|
|
Backend simplified to use compiler and linker flags on per target basis.
Removes redundant link_flags field in model structure.
Fixes benign issue with duplicated link flags.
|
|
|
|
Update subcommand "new" to reflect the addition of support for the ex…
|
|
- Include bootstrap of Fortran fpm in install.sh
- Add ability to update repository from latest tag
- Add ability to specify install path
- Update README to simplify bootstrap procedure
|
|
Include root dir in path to default example setup
|
|
Suggest to move the fpm version in the boostrapping process
|
|
Update: fpm_backend with dynamic openmp scheduling
|
|
|
|
|
