From: "peter a. cejchan" <pac@cejchan.gli.cas.cz>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] One more silly question
Date: Wed, 12 Jun 2002 12:36:33 +0000 [thread overview]
Message-ID: <71652467.0206120322.71ca293@posting.google.com> (raw)
In-Reply-To: <c9bde7f7951d9034ffa22ea14b0f3f48@plan9.bell-labs.com>
rob@plan9.bell-labs.com (rob pike, esq.) wrote in message news:<c9bde7f7951d9034ffa22ea14b0f3f48@plan9.bell-labs.com>...
> > why doesn't 'install' target in /sys/src/cmd/mklib cp also $HFILES?
>
> Because HFILES might include private implementation files that
> should not be copied.
>
> > Is this a clean solution to it?
> >
> > installh:V: install
> > cp $HFILES $home/include/
> >
>
> Sure, if that's what you want, but since when is $home an installation
> directory for system libraries? This looks like a fine rule for the mkfile
> of a private program but is not suitable for /sys/src/cmd/mklib.
>
> -rob
I did not mean to change/sys/src/cmd/mklib -- just needed a solution
for a private program(s) that need to be linked against a (non-system)
lib. perhaps it is unwise, but I keep all my stuff under $HOME
hierarchy, binding what I need to proper (?) system dirs.
++pac
next prev parent reply other threads:[~2002-06-12 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 12:52 rob pike, esq.
2002-06-12 12:36 ` peter a. cejchan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-10 8:01 Peter A. Cejchan
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=71652467.0206120322.71ca293@posting.google.com \
--to=pac@cejchan.gli.cas.cz \
--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).