Ondřej Čertík
Ondřej Čertík
> An implementation that seemed helpful enough could convince me. Brad, you should be more excited about such features. :) I was hoping you could implement it!
Indeed. I think there is a large common denominator of all Fortran compilers, that we should provide a unified interface to. This is another avenue to tackle https://github.com/fortran-lang/fpm/discussions/443, as we...
I am ok with any testing framework for `fpm` itself. The current one is fine with me. As long as `fpm test` works with any testing framework. I assume we...
Awesome, thanks! Fpm is under MIT license, is there a reason to change the tests to to Apache? It's probably a relatively minor issue, but I don't have that much...
All right then. I think Apache is fine. You should also ask anybody who contributed to this code if they are ok with the license change.
@awvwgk there are multiple ways this can be achieved, I don't know yet the best way forward. I think our requirements are: * Work with upstream fpm packages (say `stdlib`,...
Note that to fix this issue, I am imagining something like `fpm --create-spack-package` and it will take the current fpm package in the current directory, and spit out the spack...
@awvwgk I agree, that is higher priority.
I tested it and it looks like this for me: So you can see the different colors and it hides the compilation line. Yes, that is exactly what I had...
We should have tests for all of the above, then it will at least be clear what is supposed to work.