The HPE Cray Compiler Environment also has its own Makefile generator: ftnmgen
One more for the table.
This is still true of submodules if I’m not mistaken. But the parent modules must be processed first.
This wouldn’t make much sense, as pointed out in the four replies starting here: Containers using F202Y's generic programming - #29 by ashe. As Themos pointed out, even if the module format was shared, there is a realistic chance of incompatibilities in the runtime support library. It is similar to how you can’t do a malloc in C followed by a deallocate in Fortran. It wouldn’t work to have a object compiled with gfortran call allocate, and let the deallocate happen in an ifx-compiled object. The compilers use different array descriptors, different conventions, etc.
Yep. Include files can be recursive, so one has to process them as they come. Also the tool will need to correctly mimic the compiler include folder search logic to resolve preprocessor symbols.