From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Org Build System (aka Makefile) Date: Mon, 13 Aug 2012 00:27:40 +0200 Message-ID: <87r4rb690j.fsf@gnu.org> References: <87y5mkrca2.fsf@Rainer.invalid> <87ipcs3smd.fsf@Rainer.invalid> <871ujf5i7g.fsf@gnu.org> <874no8dxik.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:48608) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T0gcv-00042x-Ct for emacs-orgmode@gnu.org; Sun, 12 Aug 2012 18:27:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T0gcu-0007pw-8K for emacs-orgmode@gnu.org; Sun, 12 Aug 2012 18:27:17 -0400 Received: from mail-we0-f169.google.com ([74.125.82.169]:42079) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T0gcu-0007ps-14 for emacs-orgmode@gnu.org; Sun, 12 Aug 2012 18:27:16 -0400 Received: by weys10 with SMTP id s10so2337458wey.0 for ; Sun, 12 Aug 2012 15:27:15 -0700 (PDT) In-Reply-To: <874no8dxik.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 12 Aug 2012 15:56:35 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Achim Gratz Cc: emacs-orgmode@gnu.org Hi Achim, Achim Gratz 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