From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Org Build System (aka Makefile)
Date: Tue, 14 Aug 2012 08:13:48 +0200 [thread overview]
Message-ID: <87pq6uxaoz.fsf@Rainer.invalid> (raw)
In-Reply-To: 87ehna8lb5.fsf@gmx.com
Eric Schulte writes:
> I second the idea that a top level 'make elint' would be very useful for
> developers (see the attached patch).
I'll see to implement that when and if I get elint to process the Org
sources without throwing bogus warnings and errors because it runs into
some depth limit. Until then I will not expose it on top level.
I take it you're not using `elint-current-buffer´ before checking your
edits in… which is how it was designed to be used, anyway.
> In my opinion this would be more useful than a number of existing
> top-level targets,
> config-*,
Try to replace that functionality any other way. I could hide the
internal targets and document only the two or three that I want to be
used (see below).
> update
Compatibility.
> update2,
This was specifically requested, not that I like it very much.
> cleanall,
Compatibility.
> cleandirs, cleancontrib, cleantesting, cleanutils, cleanelc
Internal use and compatibility, I could remove the documentation if
Bastien changes his mind about all the target needing documentation.
> targets
Mandated by GNU Makefile standards which I try to adhere to.
> But many more people will use such a target if it exists at the top
> level and is mentioned by "make help".
Speculation. I know that I won't use it very much because it simply
runs far too long on my machine. An elint-dirty that just runs through
the files that have been changed would probably be much more useful, but
the time that could have been spent on trying to implement that went to
bikeshedding about which file to edit. Thanks.
You found the time and energy to edit Makefile and targets.mk, so
presumably you might be able to edit local.mk as well as I suggested
numerous times. So please go ahead and actually do it and then after
you've used elint for a while tell me how useful you find it from your
experience and if there are other things that need attending aside from
that depth limit. Get other people to use it too, and have them chime
in.
> +elint:
> + $(MAKE) -b _COMPILE_=slint3
This introduces a useless fork and GNU make doesn't even process the
'-b' option. What happens then depends on what is the default target
(which may or may not include `compile´).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html
next prev parent reply other threads:[~2012-08-14 6:14 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 [this message]
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=87pq6uxaoz.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).