Differences between version 8 and revision by previous author of AntVsMake.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 8 | Last edited on Friday, May 28, 2004 12:53:10 pm | by JamieFlournoy | Revert |
| Older page: | version 7 | Last edited on Friday, October 31, 2003 10:27:50 am | by JohnMcPherson | Revert |
@@ -3,15 +3,18 @@
Problems with Ant
# Ant's relative youth means that many developers aren't familar with it.
# Ant's relative youth means that many development support applications (editors, [IDE]'s, etc) don't support it.
# Ant's relative youth means that relatively few established projects use it.
+# Ant's relative youth means that most of the tasks it comes with aren't very well-tested or robust.
# Moving an established project from ant to make (or visa versa) is non-trivial.
# Ant depends on [Java].
# Ant lacks native support for non java-oriented packages (like [GCC] and [Bison]).
+# Ant is very, very slow compared to Make.
+# Ant's definition of "target" doesn't mean a file on disk, it means a set of tasks. This means that if you want a "set of tasks" to run only if a file is missing, you have to define a separate "target" that sets a variable if that file is available, and then your "target" that creates that file has to run unless that variable is set.
Problems with make
-# Moving an established project from ant to make (or visa
versa) is non-trivial
-# make depends on the [UNIX]/[Linux] [Shell] or a reasonably
approximation.
+# Moving an established project from ant to make (or vice
versa) is non-trivial
+# make depends on the [UNIX]/[Linux] [Shell] or a reasonable
approximation.
# Because make has been around since 1972, it has no native support for newer techniques ([UnitTesting], gzip(1), bzip2(1), signing).
# The hidious tab problem, in which a tabs and spaces are visually indistinguishable but have very different semantics.
Benefits of Ant
