From mboxrd@z Thu Jan  1 00:00:00 1970
From: tlaronde@polynum.com
Date: Wed, 11 Jun 2008 19:33:05 +0200
To: weigelt@metux.de, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-ID: <20080611173305.GA681@polynum.com>
References: <20080611124038.GA3004@nibiru.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080611124038.GA3004@nibiru.local>
User-Agent: Mutt/1.4.2.3i
Subject: Re: [9fans] Modularizing plan9port
Topicbox-Message-UUID: bad10466-ead3-11e9-9d60-3106f5b1d025

Hello,

On Wed, Jun 11, 2008 at 02:40:38PM +0200, Enrico Weigelt wrote:
>
> [...]
> So I intent do write some script which creates Makefile's from
> mkfile's and maybe even does some build-time configuration
> (sort of ./configure ;-)). That script(s) could be packet along
> with some other fundamental p9p build utils, and this package
> then would be the very first in depedency chain. Taking cross-
> builds into account, this would be an TOOL or HOST dependency,
> since it runs on the building host, not the target - an compiler-
> less target wouldn't ever need it (it plays in the same liga as
> tools like lex, make, autoconf, etc).

FWIW, and this has nothing to do with what should or should not be done
with plan9port, for this kind of stuff you can give a look at:

http://downloads.kergis.com/risk_comp_1.0C.0.1.tar.gz

(I'm the author, this is a BSD licence with public domain configuration
files. If some people find this usefull and are uncomfortable with the
licence, I can put in public domain the whole stuff. R.I.S.K. was for:
Reduced Instructions Set toolKit)

This is precisely (for POSIX right now) some simple sh(1) scripts, and
a set of sh(1) files setting variables to do this. It embeds processing
to use several parsers and scanners (lex(1) and yacc(1)) in a same
object file (I don't use this anymore, since I have understood that I
needed this due to engineering faults...)

This is not rocket science. This is simple (and limited and faulty). And
this was done to allow not using any autoHell stuff.

It has been used to successfully compile (cross-compile too) and
distribute under the *BSD, some flavors of Linux (I lost tracks of all
the variations), and Mac OSX.

The documentation is the commented scripts by themselves.

But as others more gifted have spent less time understanding than I
spent myself, putting the emphasis on these sort of tools, is like
looking to the finger when plan9 shows you the moon.

I put now together: consistancy and concision:

"hbrw, an hmg to Kn Thmpsn".

Cheers,
--
Thierry Laronde (Alceste) <tlaronde +AT+ polynum +dot+ com>
                 http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C