Damian Rouson

I'm fine with any solution that solves the problem. I suspect that the one I originally proposed is probably the easiest for `fpm` to support, albeit by offloading to the...

Another alternative would be an option to specify the manifest's location. For now, I will have the project's `install.sh` script create an OS-specific manifest in the `build` tree and then...

I too am curious about the rationale for only supporting a single library target. @awvwgk is item 2 in [your comment] the answer? Setting up separate projects for this purpose...

I'm working with collaborators on a possible successor to OpenCoarrays, which is written primarily in C. The successor will be written as much as possible in Fortran and is already...

@awvwgk thanks for considering this. I'm a minimalist so I generally put everything in default locations and most of my `fpm` manifests are 5-10 lines. Therefore I'm not very familiar...

Earlier in this thread, I mentioned wanting to produce multiple libraries from one project for my work on a successor to OpenCoarrays. The aforementioned package is now open-source and had...

@milancurcic I just realized that #682 addresses a different topic but related topic. I'm referring to module dependencies, which might be mostly internal and could exist even in a project...

@hassaniriad thanks for submitting this. I just discovered what is likely the same issue the day before you submitted this. @vehre could this be related to your recently merged PR?

Hi @jabl, That would work in the short-term, but there's ongoing discussion about implementing some parts of the `libcaf_mpi` in Fortran. If we go that route, we would definitely want...

Agreed. If you get started, I'll contribute via the time-honored copy-paste-modify method.