aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormilancurcic <caomaco@gmail.com>2020-04-29 10:27:52 -0400
committermilancurcic <caomaco@gmail.com>2020-04-29 10:27:52 -0400
commit05b86356db6fe1511e49e8345c0226ab860d02d3 (patch)
tree22d9b9aa1e9cb317691243a12f23a912dc334508
parent897dd97d09f66469a50cadacc25b5ccd8a09bc13 (diff)
downloadfpm-05b86356db6fe1511e49e8345c0226ab860d02d3.tar.gz
fpm-05b86356db6fe1511e49e8345c0226ab860d02d3.zip
remove meta notes from the packaging guide
-rw-r--r--PACKAGING.md11
1 files changed, 0 insertions, 11 deletions
diff --git a/PACKAGING.md b/PACKAGING.md
index 28043c1..9c3457e 100644
--- a/PACKAGING.md
+++ b/PACKAGING.md
@@ -100,10 +100,6 @@ $ fpm run
Hello, World!
```
-> **Issue candidate**: fpm.toml setting `main = "main.f90"` is currently hardcoded.
-
-> **Question**: How to specify multiple executable programs?
-
If your application needs to use a module internally, but you don't intent
to build it as a library to be used in other projects, you can include the
module in your program source file as well.
@@ -204,13 +200,6 @@ packages (more on this in a bit).
Since this is a library without executable programs, `fpm run` here does
nothing.
-> **Issue candidate**: `fpm run` should trigger an error if run in a project
-> without executable programs. For example:
->
-> ```
-> fpm error: This package has no executable programs.
-> ```
-
In this example, our library is made of only one module.
However, most real-world libraries are likely to use multiple modules.
Let's see how you can package your multi-module library.