From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] make out?
Date: Sat, 3 Dec 2011 00:09:40 +0100 [thread overview]
Message-ID: <20111202230940.GA3356@polynum.com> (raw)
In-Reply-To: <CAH7AAvr9FEjyEBi1npOC4y977LwZti_amKMHQr0m+Yu022K1Ug@mail.gmail.com>
On Fri, Dec 02, 2011 at 02:34:49PM -0800, Christopher Nielsen wrote:
> On Fri, Dec 2, 2011 at 14:29, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
> > make
> > nmake
> > pmake
> > bmake
> > mk
> > gmake
> >
> > i guess ant is the solution. lord knows posix could not decide on a single
> > syntax. because it would mean picking one syntax. which was against the
> > rules. unlike all the places where they did that in the C library. fecking
> > eeegits.
>
> Having had to (grudgingly) deal with ant, I would say that it is
> definitely not the solution. Ant uses XML for its syntax. I think that
> says it all.
And seeing the mess, wanting to be able to compile and cross-compile
on whatever; or wanting to not need tens of gigabytes of free space
to compile a "thing" to finally obtain tens of megabytes of programs
(solution: program the framework so that intermediary objects are
removed once the target is obtained); and definitively _not_ wanting
autoconf and automake, I have designed R.I.S.K. for KerGIS, used
now for kerTeX too (and others not published): it has taken me
even not one day of work (it for sure shows).
Not to say that R.I.S.K. is the solution. But there are a lot of threads
that take an amount of time reading sufficient to have the job done...
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2011-12-02 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 22:29 Lyndon Nerenberg
2011-12-02 22:34 ` Christopher Nielsen
2011-12-02 22:39 ` Lyndon Nerenberg
2011-12-02 23:09 ` tlaronde [this message]
2011-12-02 23:21 ` Bakul Shah
2011-12-02 23:27 ` Lyndon Nerenberg
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=20111202230940.GA3356@polynum.com \
--to=tlaronde@polynum.com \
--cc=9fans@9fans.net \
/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).