[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: autoconf / automake
- From: Dimiter 'malkia' Stanev <malkia@...>
- Date: Thu, 27 Oct 2011 14:32:54 -0700
Amalgated build. That's what SQLite is doing, and it's very easy to
import in other projects - .vcproj, XCode, makefiles, etc.
It could make sense for lua, but for luajit (although there is amalgated
build), there are some extra steps required.
As for automaketools - I was always puzzled by them. Generating
something to generate something else is fine, as long as it does not
become part of your source code distribution - there seems to be couple
of things here, but I've never bothered going in details.
Qt's qmake system was nice, and GNUStep one (based somewhat on NeXT/old
Apple makefiles is not bad either).
I don't particulary like CMake, as it's been pain in the ass for me to
use - it goes again with this generate step, and requires some extra
attention - where it should be installed, where the recipes to be found,
On 10/27/2011 11:35 AM, Michael Gogins wrote:
You could afford to always rebuild everything, so you could afford to
put all Lua source code in one .c file and build it with a single
command. Configuration of compiler options, include paths, etc. could
then be done in a script.
On Thu, Oct 27, 2011 at 11:59 AM, Luiz Henrique de Figueiredo
For the other side the Makefile of Lua itself is a good
example of how a makefile should *not* be done.
Could you please elaborate? I don't recall any major issues reported here.
The Makefiles in the Lua tarball are meant to be portable to all variants
of make that exist, not just GNU make. Just like Lua caters for ANSI C, not
GNU C. But perhaps for the Makefiles this portability is pushing it. However,
I do remember old Sun OS machines whose make was very plain. So perhaps the
question is "What is the equivalent of ANSI C for make?".