You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to more quickly distinguish between bmake and gmake files, we could create a new linter rule that warns on ambiguous files.
Basically, Makefile is ambiguous. This can lead to both text editors and humans assuming the wrong syntax. Any Makefile's can be disambiguated by adopting the fully lowercase makefile (bmake) or else GNUmakefile (gmake).
The text was updated successfully, but these errors were encountered:
On second thought, there is value in encouraging the POSIX Makefile name. Projects that do not depend on extensions to the POSIX make standard, should follow the Makefile name.
A rule to the effect of checkbashisms would be helpful. When GNU-isms or BSD-isms are present, recommend the relevant filename. Otherwise, recommend the generic Makefile.
One thing to consider here is how some build systems will automatically generate Makefiles with the Makefile name regardless of what sort of syntax they contain. It isn't really as easy to rename the files in such cases.
In order to more quickly distinguish between bmake and gmake files, we could create a new linter rule that warns on ambiguous files.
Basically,
Makefile
is ambiguous. This can lead to both text editors and humans assuming the wrong syntax. AnyMakefile
's can be disambiguated by adopting the fully lowercasemakefile
(bmake) or elseGNUmakefile
(gmake).The text was updated successfully, but these errors were encountered: