fpm icon indicating copy to clipboard operation
fpm copied to clipboard

Fortran Package Manager (fpm)

Results 249 fpm issues
Sort by recently updated
recently updated
newest added

Now that we have a dedicated repository for the fpm documentation we should try to minimize the duplication and overlap of different information sources. - [ ] move everything from...

documentation

### Description auto-build of files in the app/ directory only occurs if the file main.f90 exists. Even the case where main.f90 is renamed to main.F90 is not built. ```bash fpm...

bug

### Description If I understand correctly, `dev-dependencies` in the `fpm.toml` file specifies dependencies for development (e.g., tests), and this dependency should not be exposed to dependent projects in any way....

bug

Fpm already has a preliminary support for C and C++ source files. But there are still some issues to iron out. Here are a few that I am aware of,...

enhancement

### Description Using an fpm command which does not require to be in the project root will still attempt to find a package manifest. For fpm new this can produce...

bug

### Description `pytest` has decorators which allow for a variety of conditional executions. It would be useful to have a way of marking slow tests, or other kinds of conditional...

enhancement

### Motivation Not all parts of a project are always needed. Many Fortran projects can be build with and without MPI support for example. Currently there is no mechanism to...

specification

### Description For integration in packaging systems like conda-build or spack or to seamlessly work with environment modules fpm could allow an option to use non-prefixed environment variables. - `--compiler`,...

enhancement

Currently we attach the version number to each release artifact. If we would remove or additionally upload artifacts without the version number (`fpm.F90` instead of `fpm-0.4.0.F90`) it would be possible...

automation

Match behaviour of bootstrap version