9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Building dependencies.
Date: Thu, 20 Sep 2001 13:44:34 -0400	[thread overview]
Message-ID: <20010920174445.38C60199ED@mail.cse.psu.edu> (raw)

// We tend to keep things simple, with one header
// file for a whole program, or two if we split data
// from function declarations.  Then we just make
// everything depend on the header file (or both headers).

while i agree this is the best approach to building
systems in most cases, i ocasionally have to deal with
alien code. much, much code i've run accross isn't
built with anything approaching simplicity in mind,
nor do the makefiles tend to be readable, useful, or
workable under APE. i'd love to be able to generate the
list of dependancies and roll my own ma?ke?file.
-α.



             reply	other threads:[~2001-09-20 17:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20 17:44 anothy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-20 18:28 Alexander Indenbaum
2001-09-21  2:47 ` Boyd Roberts
2001-09-21  8:40   ` Douglas A. Gwyn
2001-09-21  9:14     ` Boyd Roberts
2001-09-21 16:06     ` David Lukes
2001-09-20 17:34 Russ Cox

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=20010920174445.38C60199ED@mail.cse.psu.edu \
    --to=anothy@cosym.net \
    --cc=9fans@cse.psu.edu \
    /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).