From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 3 Dec 2011 00:09:40 +0100 From: tlaronde@polynum.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20111202230940.GA3356@polynum.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] make out? Topicbox-Message-UUID: 4d321a36-ead7-11e9-9d60-3106f5b1d025 On Fri, Dec 02, 2011 at 02:34:49PM -0800, Christopher Nielsen wrote: > On Fri, Dec 2, 2011 at 14:29, Lyndon Nerenberg wrot= e: > > make > > nmake > > pmake > > bmake > > mk > > gmake > > > > i guess ant is the solution. =A0lord knows posix could not decide on = a single > > syntax. because it would mean picking one syntax. =A0which was agains= t the > > rules. =A0unlike all the places where they did that in the C library.= =A0fecking > > eeegits. >=20 > 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... --=20 Thierry Laronde http://www.kergis.com/ Key fingerprint =3D 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C