Commit 72eb1b11 authored by Francois-Rene Rideau's avatar Francois-Rene Rideau
Browse files
parents a644174b 30634e47
......@@ -181,3 +181,9 @@
title = {SCons website},
url = {http://www.scons.org/}
}
@Misc{ant,
key = {ant},
title = {Apache ant website},
url = {http://ant.apache.org/}
}
......@@ -1203,11 +1203,7 @@ that aim to unify the entire build chain.
These, too, aim to overcome many of the limitations of make.
The {\ant} system for Java also attempts to go beyond {\make},
in particular in using an XML dialect
to provide more declarative system specifications.
\fixme{Add citation for \texttt{ant}; a cite to the Sun Java web site would be
fine if we can't find a better. I couldn't find a nice short article.}
to provide more declarative system specifications~\cite{ant}.
\section{Future Directions}
......@@ -1399,7 +1395,7 @@ does not work for others using their new classes.
% Didn't have a good way to fix system dependencies.
% \end{itemize}
% \fixme{There are still some ickinesses here, primarily arising from the
% There are still some ickinesses here, primarily arising from the
% non-parallelism between \lisp{input-files} and \lisp{output-files}. The two
% aren't really parallel, because when we compile we use \lisp{component-pathname}
% and not \lisp{input-files}, but we still write to \lisp{output-files}, and
......@@ -1407,7 +1403,7 @@ does not work for others using their new classes.
% list doesn't have the component-pathname's fasl equivalent as its \lisp{car}.
% There's a land mine or two there for sure. Robert Brown's problems with
% defining a new component type illustrate this. Probably should add a
% paragraph explaining this.}
% paragraph explaining this.
\section{Conclusion}
\label{sec:conclusion}
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment