From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Sat,  5 Aug 2006 16:49:59 +0200
From: Christoph Lohmann <20h@r-36.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] mkfile question: mklib & co.
Message-Id: <20060805164959.60ec4362.20h@r-36.net>
In-Reply-To: <d32ac901538a3150458665b6fbc59ecd@mail.gmx.net>
References: <d32ac901538a3150458665b6fbc59ecd@mail.gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 971a7f36-ead1-11e9-9d60-3106f5b1d025

Good day.

Am Sat, 5 Aug 2006 10:34:10 +0200
"Sascha Retzki" <sretzki@gmx.de> schrieb:

> 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.

Why does this need to be in the default mk file?

installheader:
	cp *.h /sys/include

But beware that you need the rights to write there, so it is better to have
$HOME/include and bind it before /sys/include, in your profile.

> Something related: Does $objtype work in #pragma lib? If not, mk would have to put in #pragma lib to make library distribution a pleasure.

You write the library, so you put it there.

Sincerely,

Christoph