If I build a Fortran library that has an ISO C binding, and I provide C/C++ headers as a companion then I would like them to be shipped with the static library, so whoever wants to use said library have the whole solution. Currently, only Fortran module (.mod) files are shipped in library.include-dir.
Possible Solution
As a first step, let's address C/C++ headers from library.src-dir only. This way, there is no need to handle nested folders the headers may need. fpm should just parse them, include them in the list of installed files and copy them to library.include-dir.
Additional Information
An example can be seen running fpm install with fitpack.
Description
If I build a Fortran library that has an ISO C binding, and I provide C/C++ headers as a companion then I would like them to be shipped with the static library, so whoever wants to use said library have the whole solution. Currently, only Fortran module (
.mod
) files are shipped inlibrary.include-dir
.Possible Solution
As a first step, let's address C/C++ headers from
library.src-dir
only. This way, there is no need to handle nested folders the headers may need.fpm
should just parse them, include them in the list ofinstall
ed files and copy them tolibrary.include-dir
.Additional Information
An example can be seen running
fpm install
with fitpack.