# Automatic Make recipes generation

**URL:** <https://fortran-lang.discourse.group/t/automatic-make-recipes-generation/10570>\
**Category:** Announcements\
**Created:** [December 24, 2025, 9:03pm UTC](https://fortran-lang.discourse.group/t/automatic-make-recipes-generation/10570 "2025-12-24T21:03:24Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![ivanpribec](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ivanpribec/32/3290_2.png) [@ivanpribec](https://fortran-lang.discourse.group/u/ivanpribec)\
**Post date:** [January 7, 2026, 2:04am UTC](https://fortran-lang.discourse.group/t/automatic-make-recipes-generation/10570/8 "2026-01-07T02:04:19Z")

</div>

The HPE [Cray Compiler Environment](https://cpe.ext.hpe.com/docs/24.11/cce/index.html) also has its own Makefile generator: [`ftnmgen`](https://cpe.ext.hpe.com/docs/24.11/cce/man1/ftnmgen.1.html)

One more for the table.

* * *

> [@urbanjost](#):
>
> The biggest think I miss about pre-module Fortran is being able to compile things in just about any order I wanted independently of other files.

This is still true of submodules if I’m not mistaken. But the parent modules must be processed first.

> [@urbanjost](#):
>
> A standard format for \*.mod files that could be included in a an archive (\*.a) file or equivalent would sure be nice too.

This wouldn’t make much sense, as pointed out in the four replies starting here: [Containers using F202Y's generic programming - #29 by ashe](https://fortran-lang.discourse.group/t/containers-using-f202ys-generic-programming/10484/29). 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.

> [@urbanjost](#):
>
> complications always include handling cpp pre-processor directives and #include

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.

---

_[View the full topic](https://fortran-lang.discourse.group/t/automatic-make-recipes-generation/10570)._