lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GOP-PROP 5: build system output (probable decision)


From: Phil Holmes
Subject: Re: GOP-PROP 5: build system output (probable decision)
Date: Sun, 24 Jul 2011 17:37:28 +0100

----- Original Message ----- From: "Graham Percival" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: <address@hidden>; "Ian Hulin" <address@hidden>
Sent: Sunday, July 24, 2011 5:11 PM
Subject: Re: GOP-PROP 5: build system output (probable decision)


On Sun, Jul 24, 2011 at 03:32:20PM +0100, Phil Holmes wrote:
----- Original Message ----- From: "Ian Hulin" <address@hidden>
To: <address@hidden>
Sent: Sunday, July 24, 2011 12:33 PM
Subject: Re: GOP-PROP 5: build system output (probable decision)

>1+ for Graham's proposal, provided his bin target acts as a synonym for
>exe, and builds all the stuff in out/bin.

If we go with my proposal (which is nice and simple as a starter) it
will simply remake the .exe if any file in \lily is changed.  This
strikes me as a handy first step and would speed the development
process up.

I like it.

>Graham, what are the time estimates for adding a top-level make target
>for developer who's a build-system virgin?

For a build-system virgin -- which you don't qualify as, since you
already a bit about build systems -- I'd say 2 hours.  For you,
maybe 1 hour.

It'd take me about 5 minutes.

I'm calling it 30 minutes, including testing, patch for review,
revising the patch to accommodate comments, testing+uploading new
patch, etc.

Start your stopwatch.  :)

Cheers,
- Graham


Patch attached. Not convinced it's worth a Rietveld for essentially one line? Works on my system.

--
Phil Holmes

Attachment: 0001-Creates-make-bin-command.patch
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]