Re: DOCS: include a sample "Makefile"?

[Ian Hulin]

Jonathan Kulp wrote:
> Werner LEMBERG wrote:
> > > What do you guys think of including a sample Makefile somewhere in
> > > the documentation?
> >
> > Good idea!  Perhaps we can manage to avoid GNU make extensions so that
> > poor Windows users have a chance to try nmake.
> >
> >
> >     Werner
>
> I've been working on it for a while now and have added a section on 
> Makefiles to working.itely, the very last thing in the LM that appears 
> before all the templates.  I would welcome comments on it before I 
> commit and make a patch.  A pdf of the appropriate section is available 
> here:
>
> http://www.jonathankulp.com/makefiles.pdf

Hi Jon,

Call the section and do a bit of explaining upfront of what this is 
(this is the LR, after all)

-5.4 Makefiles
+5.4 Make and Makefiles
+Pretty well all the platforms Lilypond can run on support a software 
+facility called /make/.  This software reads a special file called a 
+/makefile/ that defines what files depend on what others and, what 
+commands you need to give the operating system to produce one file form 
+another.  For example the makefile would spell out how to produce 
+ballad.pdf and ballad.midi from ballad.ly by running Lilypond.

There are times. . .
.
.
.
... available for Windows.

-There are detailed instructions on creating Makefiles in the *Gnu Make 
-Manual*, but we offer here a few sample Makefiles for use with Lilypond 
-projects.

+Have a look at the *GNU Make Manual* for full details on using make, 
+but here are a few simple example makefiles you could use for Lilypond 
+projects.
+
+Some of the platforms differ in the commands needed to specify rules 
+for defining the rules in a makefile; for instance the various forms of 
+Linux and MacOS use /bash/, while Windows uses /cmd/.  Here are some 
+example makefiles, with versions for both Linux/Mac-OS and Windows. 
+Note that on MacOS-X, you need to configure the system to use the 
+command-line intepreter.

-Due to differences between Windows and the Unix-style oprating systems, 
-there are separate examples for each.  Note that on Mac OSX, the system 
-must be configured for command-line usage.

<The only other comment I'd have is
-Save the following code as build.bat.
+Save the following code as build.bat or build.cmd.

> I'd be especially keen to hear if someone has a better way to display 
> the directory structure of the sample project, as it takes up quite a 
> bit of space.
I think John M. gave you this one in an earlier reply.

> Thanks for input :)
>
> Jon

Well done for all the effort you've put in.

Cheers,

Ian Hulin