From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8c73654c50ebbfb53e546947ffb2e30a@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Sat,  5 Aug 2006 09:37:36 -0500
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mkfile question: mklib & co.
In-Reply-To: <40e1ba97a9edf4e3a37fd5174b4b1055@mail.gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 96fc81f2-ead1-11e9-9d60-3106f5b1d025

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?