From: Bastien <bzg@gnu.org>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: Org Build System (aka Makefile)
Date: Mon, 13 Aug 2012 15:45:20 +0200 [thread overview]
Message-ID: <874no6zz0v.fsf@gnu.org> (raw)
In-Reply-To: <87boifrkyl.fsf@gmx.com> (Eric Schulte's message of "Mon, 13 Aug 2012 07:16:18 -0600")
Let's summarize.
It is no a matter of "exposing the user to the warnings" or not.
It is a matter of exposing the user to the warnings that might be
useful to him -- i.e. the ones he might want to report to the list
just to let the developers know, or in the context of a bug hunt.
The warnings you get by compiling Elisp files within a single Emacs
process are *not* useful to the users because these warnings happen
during context-free compilation, and as such, they are not relevant to
what the user evaluates when he loads Org (even worse: those warnings
may lead him to misinterpret what is missing at run time, whereas they
warn about things that are missing at comile time.)
So let's stick to the current default `make' for compilation.
However, I would suggest these changes to the current default.mk:
- Have a target `make single' (useful for developers)
- `make test' should use the default make compilation (within one
Emacs process), because this target is primarily for performing
tests, not for checking warnings.
- `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' would run the current `make _COMPILE_=slint3'.
- `make elint single' would run the current `make _COMPILE_=slint4'
(even though I would not complain if we get rid of this target.)
- Let's get rid of the _COMPILE_ variable: it is not handy to have
to edit this just for running checks.
I hope our brains now all compile fine within the same context. :)
Achim, if you are okay with the suggestions above, can you make the
relevant changes?
Thanks!
--
Bastien
next prev parent reply other threads:[~2012-08-13 13:45 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 [this message]
2012-08-13 19:27 ` Achim Gratz
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=874no6zz0v.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.com \
/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).