Hello Marko and all,
Some time ago I start to write something alike, but for cmake and not for make.
I.e. my scripts bunch is dedicated for:
- easer porting to cmake from exists autoconf based build system
- easer write autoconf oriented software
Scripts itself is not a build system but a library in which I've been a tried
one-to-one translation of main autoconf functions from m4 to cmake language.
FYI I've been uploaded them to gihub: https://github.com/avolkov1221/autocmake
And yes scripts IMHO in alpha stage (meanwhile some functions are implemented
and working) yet so comments are welcomed.
--
Regards
Andrey Volkov
10.03.2012 21:33, Marko Kreen wrote:
On Sat, Mar 10, 2012 at 09:52:10AM +0900, Miles Bader wrote:
Any sense on how it compares to quagmire?
From quick look:
1. Quagmire tries to replace autoconf and libtools too,
Antimake is strictly build tool. It leaves system
detection to autoconf and shared libs to libtool.
2. Despite that, Quagmire seems to depend autoconf for
initial setup. Antimake has defaults for anything
and can operate standalone.
This means that Antimake is also usable also for small
or even throwaway test projects, which Automake or
Quagmire isn't.
3. Antimake is single file, you can simply add it into your source
tree and never worry about incompatibility with newer versions.
As it does not contain any system-specific knowledge, the need
to upgrade should be small also, if the features used in project
are working well.
