Add [install] section to fpm.toml

[moriglia]

Moved PR from stdlib-fpm to master branch.

Initial discussion here: #903

[moriglia]

Another thing I noticed is that fpm will use the project name in the library archive, i.e. stdlib.
In contrast, in this section of the README, the suggested flag and name is fortran_stdlib.

Should I also change the project name to fortran_stdlib to have fpm produce libfortran_stdlib.a instead of libstdlib.a?

[perazz]

LGTM, thank you @moriglia.

Regarding the fpm library name, I believe it should remain stdlib, because that is the name that is typically used as a fpm dependency (including as a "metapackage").

[moriglia]

Thank you! @perazz
Somehow it felt wrong to link against a fortran_stdlib to me, also :)

[moriglia]

Ok, thanks, got it! I'll fix and amend my latest commit as soon as I'm back to my laptop.

…

On December 15, 2024 15:20:26 GMT+01:00, jalvesz ***@***.***> wrote: @jalvesz commented on this pull request. > @@ -219,7 +219,29 @@ python config/fypp_deployment.py --help git checkout stdlib-fpm fpm build --profile release ``` -#### Runing the examples + + +#### Installing with fpm + +Either option you chose for building the `stdlib`, you can install it with: +```sh +fpm install --profile release +``` +The command above will install the following files: +- `libstdlib.a` into `~/.local/lib/` Same pattern, what changes is that longer root, so it would be: `C:\Users\<username>\AppData\Roaming\local\lib` and `C:\Users\<username>\AppData\Roaming\local\include` -- Reply to this email directly or view it on GitHub: #906 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[jalvesz]

I think this PR can be merged. Let's wait a couple of days and if there are no remarks I'll merge it.