Re: "makefiles" vs. "Makefiles" vs. "make files"

Subject: Re: "makefiles" vs. "Makefiles" vs. "make files"
From: Robert Lauriston <robert -at- lauriston -dot- com>
To: Monique Semp <monique -dot- semp -at- earthlink -dot- net>, TechWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 20 Nov 2015 08:32:50 -0800

The convention in UNIX / Linux docs is generally to follow the
capitalization of the code. The command is make. The input file can be
named makefile or Makefile, or sometimes other things, such as
MAKEFILE or GNUmakefile. The common practice of using Makefile is so
it appears higher in directory listings.

On Thu, Nov 19, 2015 at 7:00 PM, Monique Semp
<monique -dot- semp -at- earthlink -dot- net> wrote:
> Hello, TechWR-L-ers,
> So for building instructions that are applicable to a huge variety of operating systems (and so they wonât all use the usual Linux make utility, but they will all use the supplied Makefile.<os> or Makefile.<product> pre-configured make files), how would it be best to refer to the group of supplied make files:
> * makefiles
> * Makefiles
> * make files
> The last (âmake filesâ) is certainly the most generic. But given that the actual filenames are all âMakefile.<something>â, I can see the logic for referring to them as âMakefilesâ. But if the reference isnât at the start of the sentence, the upper-case makes it appear more as a proper noun, which isnât what I want to convey. (Although the actual Make utility is always uppercase, as in this Wikipedia article: And this same article seems to use âmakefileâ, lowercase, to refer to these things generically. So thatâs what Iâm leaning toward.)
Visit TechWhirl for the latest on content technology, content strategy and content development |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

"makefiles" vs. "Makefiles" vs. "make files": From: Monique Semp

Previous by Author: Re: Do you still ship PDFs with your software?
Next by Author: Re: XML to HTML conversion....
Previous by Thread: RE: "makefiles" vs. "Makefiles" vs. "make files"
Next by Thread: RE: PDF filenames - include release designation ?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads