[Makefile] Re-compile if FLAGS change

[Makefile] Re-compile if FLAGS change

[Jambunathan K]

[-- Attachment #1: Type: text/plain, Size: 169 bytes --]


Apply the following patch and regenerate the html manual.  You will see
that the manual doesn't get *re*-generated.  Can someone review the
current rules to DTRT?

-- 

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: scraps1.diff --]
[-- Type: text/x-diff, Size: 344 bytes --]

diff --git a/default.mk b/default.mk
index 7bdb7df..af871b6 100644
--- a/default.mk
+++ b/default.mk
@@ -103,7 +103,7 @@ MKDIR	= install -m 755 -d
 MAKEINFO = makeinfo
 
 # How to create the HTML file
-TEXI2HTML = makeinfo --html --number-sections
+TEXI2HTML = makeinfo --html --number-sections --no-headers
 
 # How to find files
 FIND	= find

Re: [Makefile] Re-compile if FLAGS change

[Jambunathan K]

Jambunathan K <kjambunathan@gmail.com> writes:

> Apply the following patch and regenerate the html manual.

Clarification: This is not a patch to Orgmode.  Just a local change I
needed.

-- 

Re: [Makefile] Re-compile if FLAGS change

[Achim Gratz]

Jambunathan K writes:
> Apply the following patch and regenerate the html manual.  You will see
> that the manual doesn't get *re*-generated.  Can someone review the
> current rules to DTRT?

They do the right thing.  Make considers sources vs. targets, not
recipes vs. targets.  In this case, a simple "make clean" tells it
you've changed the environment and do want to start from sources again.

BTW, you shouldn't edit default.mk for local configuration, which is
registered with Git (this is especially important since you have push
access to the upstream repo and migth inadvertently publish your
changes).  Edit local.mk instead, which is under your control and never
clashes with anything upstream.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves