Skip to content

Conversation

@awvwgk
Copy link
Member

@awvwgk awvwgk commented Jun 20, 2021

Some projects don't store the version number in the build files but in a separate file. This allows to have central place for all tools to retrieve the version number from rather than multiple redundant version number entries.

@awvwgk awvwgk added the specification Issue regarding fpm manifest and model label Jun 20, 2021
Copy link
Member

@LKedward LKedward left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cheers, this is a useful addition.

I was thinking this could be good for fpm, where the version information is currently in two different places, but I'd probably prefer to have the version string made available to the compiler preprocessor as a definition to avoid having to locate the version file at runtime. But we haven't really looked into preprocessor defines yet for fpm.

These changes here are quite straightforward and are in line with other build systems, so LGTM.

Copy link
Member

@milancurcic milancurcic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice addition, thank you. I left one suggestion.

@LKedward
Copy link
Member

With two approvals I'll now merge. Thanks @awvwgk

@LKedward LKedward merged commit d693d68 into fortran-lang:master Jun 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

specification Issue regarding fpm manifest and model

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants