From: Robert Raschke <rtrlists@googlemail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] `mk` (from Plan9 ports) efficiency related issue
Date: Mon, 17 Jan 2011 15:53:42 +0000 [thread overview]
Message-ID: <AANLkTinzp9f4MkaP2r+yyKEuO5QJQ9T8EBJT6D_yrKY8@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimW7DGwc84ZpWiEmP0OycA8cGv+SCpPs8n3ztmQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]
On Mon, Jan 17, 2011 at 3:33 PM, Ciprian Dorin Craciun <
ciprian.craciun@gmail.com> wrote:
> On Mon, Jan 17, 2011 at 17:00, Robert Raschke <rtrlists@googlemail.com>
> wrote:
> > Your email also doesn't explain why you cannot generate a "normal"
> > mk file.
>
> I'm afraid I don't understand the question. What do you mean by
> "generating a normal mk file"?
> A) Do you mean why am I using a generator that writes the `mk`
> script instead of writing the `mk` script myself by hand? The answer
> to this is complexity: writing `mk` is Ok when you have a simple
> application to build, but as the application grows larger so does the
> make script. (And using meta rules is not always possible.)
> B) Why isn't the output script a "normal" `mk` script? Actually is
> a very simple script (no meta-rules, no shell expansion, etc.). It's
> just big. :)
>
>
Sorry, I meant an idiomatic mk file, in the sense as they are used within
the Plan 9 distribution. Have a look at "Plan 9 Mkfiles" (
http://www.cs.bell-labs.com/sys/doc/mkfiles.html) and "Maintaining Files on
Plan 9 with Mk" (http://www.cs.bell-labs.com/sys/doc/mk.html), if you
haven't already done so.
I think by listing all your dependencies one by one, step by step, you are
bypassing a lot of the strengths of a make system. I would expect your
generator to produce a mk include file with the meta rules plus the mk file
itself which lists file dependencies in a concise manner.
Robby
[-- Attachment #2: Type: text/html, Size: 2098 bytes --]
next prev parent reply other threads:[~2011-01-17 15:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 14:47 Ciprian Dorin Craciun
2011-01-17 14:59 ` erik quanstrom
2011-01-17 15:05 ` Ciprian Dorin Craciun
2011-01-17 16:50 ` Bakul Shah
2011-01-17 16:56 ` erik quanstrom
2011-01-17 18:36 ` Bakul Shah
2011-01-17 19:33 ` Ciprian Dorin Craciun
2011-01-17 19:59 ` Ciprian Dorin Craciun
2011-01-17 20:30 ` Bakul Shah
2011-01-17 15:00 ` Robert Raschke
2011-01-17 15:02 ` Robert Raschke
2011-01-17 15:18 ` erik quanstrom
2011-01-17 15:33 ` Ciprian Dorin Craciun
2011-01-17 15:51 ` Federico G. Benavento
2011-01-17 15:53 ` Robert Raschke [this message]
2011-01-17 16:02 ` andrey mirtchovski
2011-01-17 16:45 ` Ciprian Dorin Craciun
2011-01-17 17:31 ` Ciprian Dorin Craciun
2011-01-17 17:46 ` Federico G. Benavento
2011-01-17 17:51 ` Federico G. Benavento
2011-01-18 6:09 ` Andy Spencer
2011-01-18 13:26 ` erik quanstrom
2011-01-17 15:21 ` Ciprian Dorin Craciun
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTinzp9f4MkaP2r+yyKEuO5QJQ9T8EBJT6D_yrKY8@mail.gmail.com \
--to=rtrlists@googlemail.com \
--cc=9fans@9fans.net \
/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.
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 NNTP newsgroup(s).