From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Org Build System (aka Makefile)
Date: Sun, 12 Aug 2012 15:56:35 +0200 [thread overview]
Message-ID: <874no8dxik.fsf@Rainer.invalid> (raw)
In-Reply-To: 871ujf5i7g.fsf@gnu.org
Bastien writes:
> Please make the default "make" procedure display all warnings that the
> user would see by compiling Emacs itself.
That isn't even possible, you'd need to use Emacs' build system (which,
btw gives inconsistent results for repeated compiles).
> I know we disagree about this: you think that compiler warnings are for
> the developers, not for the users. I think the default "make" should
> send as much warnings as Emacs sends with its own default "make".
You continue to misunderstand what I was saying or at least trying to
say. The primary function of Org's build system is to, well, build Org
with the minimum fuzz. That's what it was designed to do and that is
what it does — it can do other things as well, but you'll have to
configure it to do that.
Getting more warnings is a secondary function, however useful they might
be. Now, Emacs Lisp as a dynamic language is notoriously difficult in
the static checks department (warnings are but a small part of that) and
Emacs lacks functions to do this thoroughly in an automated manner.
There is _no_ complete tool for doing dependency checks at the source
level (I'd love to be proved wrong) for instance. Emacs does have elint
since version 23, which is properly separated from building, but again,
is still incomplete. I've added two compilation methods that use elint,
but they certainly aren't for casual use — the first one takes 25 times
as long as a simple build and the other one 275 times.
> If a user wants the compilation to go faster, he can always use another
> instruction (the current "make" -- renamed "make quiet"?)
And by the same argument, everybody can just as well add the line
_COMPILE_=single
to local.mk if wanted. This gives _different_ warnings (and in general
more), but it is still no substitute for static checks and testing. I'm
not going to degrade the build performance for everyone to save a
handful of people the bother of doing that. If you insist, do the
change yourself (it's defined in default.mk).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2012-08-12 13:56 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 [this message]
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
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=874no8dxik.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).