From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Org Build System (aka Makefile) Date: Wed, 15 Aug 2012 00:45:13 +0200 Message-ID: <87r4r9xfd2.fsf@gnu.org> References: <87y5mkrca2.fsf@Rainer.invalid> <87ipcs3smd.fsf@Rainer.invalid> <871ujf5i7g.fsf@gnu.org> <874no8dxik.fsf@Rainer.invalid> <87k3x4rlb2.fsf@gmx.com> <87zk5zdery.fsf@Rainer.invalid> <87boifrkyl.fsf@gmx.com> <874no6zz0v.fsf@gnu.org> <877gt2oami.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:45609) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T1Pr0-0004Tr-Cg for emacs-orgmode@gnu.org; Tue, 14 Aug 2012 18:44:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T1Pqz-0004Ql-G0 for emacs-orgmode@gnu.org; Tue, 14 Aug 2012 18:44:50 -0400 Received: from mail-wi0-f171.google.com ([209.85.212.171]:37855) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T1Pqz-0004Qh-8f for emacs-orgmode@gnu.org; Tue, 14 Aug 2012 18:44:49 -0400 Received: by wibhq4 with SMTP id hq4so4011255wib.12 for ; Tue, 14 Aug 2012 15:44:48 -0700 (PDT) In-Reply-To: <877gt2oami.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 13 Aug 2012 21:27:49 +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, I reverted the commits introducing the _COMPILE_ variable and the elint targets in the makefile. I'm with Eric on thinking that even the casual developer should not have to tweak his local.mk to run the equivalent of `make compile-single', as it is directly useful to get some warnings. Even further: if a user reports a bug and we want to give him directions to get more information on his environment, asking him to run `make compile-single' is simple. As for elint, your last email shows this is still largely experimental and I doubt many developers use it to get useful warnings. Maybe `make elint' would be useful at some point, but for now developers can simply do M-x elint-current-buffer RET if they want. I also reduced the number of targets displayed by `make targets': only the ones that may be directly useful to the user or the developers are shown. You were right on this -- I first needed all doc to be able to follow your development myself... I hope you'll understand the choices above. Best, -- Bastien