From: Bastien <bzg@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org Build System (aka Makefile)
Date: Mon, 13 Aug 2012 00:27:40 +0200 [thread overview]
Message-ID: <87r4rb690j.fsf@gnu.org> (raw)
In-Reply-To: <874no8dxik.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 12 Aug 2012 15:56:35 +0200")
Hi Achim,
Achim Gratz <Stromeko@nexgo.de> writes:
> 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.
This I understood perfectly :)
> 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.
Please refrain from adding such new targets to the Makefile for
now. Let's settle the issue first.
> 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).
One thing I need to understand: what are the warnings that you have
when compiling within a single process and you don't when compiling
with one process per file?
The next thing I'd like to know is _why_ -- but even a rough answer
to the first question would help me take a decision about this.
Thanks,
--
Bastien
next prev parent reply other threads:[~2012-08-12 22:27 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
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 [this message]
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=87r4rb690j.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=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).