9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mkfile question: mklib & co.
Date: Sat,  5 Aug 2006 09:37:36 -0500	[thread overview]
Message-ID: <8c73654c50ebbfb53e546947ffb2e30a@quanstro.net> (raw)
In-Reply-To: <40e1ba97a9edf4e3a37fd5174b4b1055@mail.gmx.net>

it's just different.  having knowledge of modern unix impedes understanding
of plan 9 in the same way that basic programming impedes one's ability
to learn how to program. (yup.  i startedwith integer basic.)

i'm not sure what HFILES are used for other than mk update, which i haven't used.
i think this is superceeded by pull.

in general, plan 9 libraries don't install header files as part of their mk process.
the header files are just put where they belong to begin with.

- erik

On Sat Aug  5 09:38:18 CDT 2006, sretzki@gmx.de wrote:
> > the source goes in /sys/src/libfu.  e.g. /sys/src/libdraw.
> > 
> 
> Okay, so using /sys/src/cmd/mklib is not what I want. I found libdraw using /sys/src/cmd/mksyslib, and draw.h is copied to 'one of the' include-dirs, but I don't see it cp $HFILES to /sys/include/ *scratchhead*
> 
> Is it me or is this all a bit overcomplicated?
> 
> > - erik
> > 
> > On Sat Aug  5 09:29:08 CDT 2006, sretzki@gmx.de wrote:
> >> > there are no libraries in /sys/src/cmd and no header files which originate in
> >> > /sys/src/cmd that end up in /sys/include or /$objtype/include (modulo ape).
> >> 
> >> Ah okay, did not notice.
> >> 
> >> > libraries should go in /sys/src/libfu.
> >> 
> >> Hm?
> >> 
> >> You mean, the binaries?


  reply	other threads:[~2006-08-05 14:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-05  8:34 Sascha Retzki
2006-08-05 14:06 ` erik quanstrom
2006-08-05 14:27   ` Sascha Retzki
2006-08-05 14:19     ` erik quanstrom
2006-08-05 14:37       ` Sascha Retzki
2006-08-05 14:37         ` erik quanstrom [this message]
2006-08-05 14:52       ` Christoph Lohmann
2006-08-05 15:15         ` erik quanstrom
2006-08-05 14:49 ` Christoph Lohmann
2006-08-05 17:06   ` Sascha Retzki
2006-08-05 15:42 ` Russ Cox
2006-08-05 20:27   ` Charles Forsyth

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=8c73654c50ebbfb53e546947ffb2e30a@quanstro.net \
    --to=quanstro@quanstro.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).