ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <gudnabr...@yahoo.com>
Subject Re: incremental compilation
Date Mon, 23 Mar 2009 20:34:10 GMT

For a cheap, quick fix, try using a dependset and either searching your src tree for files
with constants, or hard-coding the list (you could keep them in a separate file if that helps).

-Matt

--- On Mon, 3/23/09, David Weintraub <qazwart@gmail.com> wrote:

> From: David Weintraub <qazwart@gmail.com>
> Subject: Re: incremental compilation
> To: "Ant Users List" <user@ant.apache.org>
> Date: Monday, March 23, 2009, 3:11 PM
> When I was a C developer, we had
> similar dependency issues with C and
> Make. Changing a static constant in one source file didn't
> cause all
> objects to recompile .And, if we didn't put it in our
> Makefiles,
> changing a *.h file didn't necessarily recompile the source
> code that
> depended upon it. We just had to know these things. It's
> why they paid
> us the big money. Well, not the big money, but we did get
> stock
> options.
> 
> Java's dependency tree rebuilding (which is really part of
> Java and
> not Ant) is no worse than what we previously had in other
> programming
> languages. It works about 99% of the time, and you simply
> had to know
> when it might not work and redo a clean build.
> 
> To get TRUE dependency checking, you'll have to get
> something like
> ClearCase and use dynamic views. ClearCase tracks all
> dependencies for
> all built objects. Of course it is slow and expensive which
> is why not
> too many other version control systems do it.
> 
> On Sat, Mar 21, 2009 at 9:52 AM, Sven Köhler <sven.koehler@gmail.com>
> wrote:
> > Hi,
> >
> > according to the docs it seems, that ant is (still)
> not suitable for
> > incremental compilation. Is that true?
> >
> > Quote from the docs of the depend task:
> >
> >
> ********************************************************************
> > The most obvious example of these limitations is that
> the task can't tell
> > which classes to recompile when a constant primitive
> data type exported by
> > other classes is changed. For example, a change in the
> definition of
> > something like
> >
> > public final class Constants {
> >  public final static boolean DEBUG=false;
> > }
> >
> > will not be picked up by other classes.
> >
> ********************************************************************
> >
> >
> > Yes, the good constant-inlining. So there is really
> nothing implemented to
> > detect that? That is: if I don't do an "ant clean"
> once in a while, then i
> > will have inconsistent class files?
> >
> > I'm rather amazed. But the trouble seems to be, that
> modern javac doesn't
> > generate any dependency information in addition to or
> inside the class
> > files. Is that right?
> >
> >
> > Regards,
> >  Sven
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> > For additional commands, e-mail: user-help@ant.apache.org
> >
> >
> 
> 
> 
> -- 
> --
> David Weintraub
> qazwart@gmail.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
> 
> 


      

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message