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:06:23 -0500	[thread overview]
Message-ID: <c33383d460450a9113494a5bfa83044e@quanstro.net> (raw)
In-Reply-To: <d32ac901538a3150458665b6fbc59ecd@mail.gmx.net>

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).
libraries should go in /sys/src/libfu.

these are the mkfiles that include /sys/src/cmd/mklib

; grep mklib `{find . | grep /mk}
./cmd/cc/mkfile:</sys/src/cmd/mklib
./cmd/map/libmap/mkfile:</sys/src/cmd/mklib
./cmd/plot/libplot/mkfile:</sys/src/cmd/mklib
./cmd/postscript/common/mkfile:</sys/src/cmd/mklib
./cmd/upas/common/mkfile:</sys/src/cmd/mklib
./cmd/usb/lib/mkfile:</sys/src/cmd/mklib

- erik

On Sat Aug  5 03:34:59 CDT 2006, sretzki@gmx.de wrote:
> 
> Hello list,
> 
> 
> got a question regarding /sys/src/cmd/mklib, why aren't HFILES copied to /$objtype/include?
> 
> I mean, the library itsself is copied to LIBDIR, \o/ , but the headerfiles are not copied. It would be great if mk can at least copy them.
> 
> Something related: Does $objtype work in #pragma lib? If not, mk would have to put in #pragma lib to make library distribution a pleasure.
> 
> 
> Or did I miss something so this all would work without problems?
> 
> 
> Mfg, Sascha
> 


  reply	other threads:[~2006-08-05 14:06 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 [this message]
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
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=c33383d460450a9113494a5bfa83044e@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).