emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Org Build System (aka Makefile)
Date: Mon, 13 Aug 2012 21:27:49 +0200	[thread overview]
Message-ID: <877gt2oami.fsf@Rainer.invalid> (raw)
In-Reply-To: 874no6zz0v.fsf@gnu.org

Bastien writes:
> However, I would suggest these changes to the current default.mk:

These changes do not belong into default.mk — default.mk is the fallback
for when no changes to local.mk have been made.

> - Have a target `make single' (useful for developers)
>
> - `make elint' would run the current `make _COMPILE_=slint3'.

I don't like such proliferation of toplevel targets since they can't be
overridden by users, things like this (an alias) are easy enough to set
up in local.mk:

--8<---------------cut here---------------start------------->8---
single:	_COMPILE_=single
single:	compile
elint:  _COMPILE_=slint3
elint:  compile
--8<---------------cut here---------------end--------------->8---

That was (and still is) the point of having local.mk — putting
customized functionality on top of the standard make mechanism.

> - `make test single' should run the tests *and* compile each file
>   in a separate Emacs process -- so that it gives as much info as
>   the developers may desire.
>
> - `make elint single' would run the current `make _COMPILE_=slint4'
>   (even though I would not complain if we get rid of this target.)

Make doesn't work that way, you can't give it two targets and hope for
it to combine these into something else.

> - Let's get rid of the _COMPILE_ variable: it is not handy to have 
>   to edit this just for running checks.

I need to keep it for communication with the sub-make in lisp/, although
I'll probably rename it to something shorter.  There's a reason
everything is set up the way it is and it actually becomes more
complicated rather than easier if I do it differently.

I'd rather provide a sample local.mk for developers that implements
these suggestions.


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

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2012-08-13 19:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15 20:37 Org Build System (aka Makefile) Achim Gratz
2012-07-15 21:38 ` Bastien
2012-08-09 17:03 ` Achim Gratz
2012-08-10  7:17   ` Bastien
2012-08-12 13:56     ` Achim Gratz
2012-08-12 18:56       ` Eric Schulte
2012-08-12 20:41         ` Achim Gratz
2012-08-13 13:16           ` Eric Schulte
2012-08-13 13:45             ` Bastien
2012-08-13 19:27               ` Achim Gratz [this message]
2012-08-13 22:43                 ` Eric Schulte
2012-08-14  6:13                   ` Achim Gratz
2012-08-14 12:46                     ` Eric Schulte
2012-08-14 22:06                     ` Bastien
2012-08-15 16:35                       ` Achim Gratz
2012-08-14 22:45                 ` Bastien
2012-08-15 17:55                   ` Achim Gratz
2012-08-15 18:56                     ` Bastien
2012-08-13 19:47             ` Achim Gratz
2012-08-14 22:07               ` Bastien
2012-08-12 22:27       ` Bastien
2012-08-13  6:11         ` Achim Gratz
2012-08-13  7:40           ` Bastien
2012-08-13 11:42             ` Achim Gratz
2012-08-13 13:13               ` Bastien
2012-08-13 14:17                 ` Achim Gratz
2012-08-13 14:48                   ` Bastien
2012-08-13 18:56                     ` Achim Gratz
2012-08-13  5:34       ` Bastien
2012-08-12 16:58     ` Samuel Wales

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877gt2oami.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).