Re: The ever lasting fight by the amule "team"
> my post isn't a flame.. it's only the
> truth about Carlo (known as Aleric or
> Run) lies ..
Right. What this shows is two-fold:
1) Freshmeat should allow the damn owners of a project to delete stupid flames like this that are totally composed by members of a very juvenile, hostile fork of our application.
2) That like alcoholics who never claim they are drunk, deltaHF always believes he is never an asshole :-)
Now you know what I deal with on a daily basis from that script-kiddy community ::sigh::
MakeNG is the answer!
MakeNG (http://makeng.sf.net/ (http://makeng.sf.net/) is made by a fellow wxWindows user, a really cross-platform GUI framework (w/ threads, sockets, et al).
MakeNG supports procedures, conditional statements, complex dependencies, and high-level script statements.
Unlike other makesystems, it is a patched version of GMake, which means it is COMPLETELY backwards compatible .. .the user won't even know they are using a MakeNG file if they have it installed on their system!
It *can* use Autoconf just fine, as my project, xMule, heavily demonstrates (http://freshmeat.net/projects/xmule (http://freshmeat.net/projects/xmule)). xMule has over 300 C++ files, requires 5 libraries, and has 2 internal libraries. MakeNG can build these with justa bout 50 lines of code!
Here's a quick peak of the main Makengfile:
var-submake-makefile := Makengfile
`$(WX_CONFIG_PATH) --libs` $(LIBS))
Compilation.flags is created either by Autoconf or MakeNG, which ever is first. Thus there is no real reason to run ./configure except out of habit.
One of the best features of MakeNG is that you can also include regular gmake code!! It is *heavily* documented (80KB of documentation) and has tons of examples (128KB) plus extending it is SOOO simple, just a matter of editing high-level script files!