>>As soon as my application grow and more classes are created, I'm
>>beginning to feel the weight of a full scale compilation (like 20
>>seconds now, but it's increasing fast) even after I change 1 line of
>>code in 1 class.
>We use make to great advantage. Our system has ~1000 java files and
>make reduces compile time dramatically. ( We use jikes, too, so that
>helps. )
I've found that with Jikes, it's best just to recompile everything.
I have a Java system that's currently 280 .files, 36000 lines of code.
It also links to 5 or 6 extra jar files. Using jikes, it takes less
than 5 seconds to compile all 280 files at once. It takes about the
same amount of time to use jikes to compile one file. It's faster to
compile everything at once than to recompile two files separately.
I guess the optimal thing would be to tell Jikes to only compile the
files that had changes. But given the complexity of doing that with
make, not to mention finding/maintaining Java dependencies, it's just
better to recompile all files each time.
Make sure your .java and .class files are not going through NFS. We
keep everything on local disk and use CVS for backups to reliable
storage.
I do use make for the files I run rmic on. There the dependencies are
easy, and rmic is very slow. Someone should write a perl replacement.
[EMAIL PROTECTED]
. . . . . . . . http://www.media.mit.edu/~nelson/
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
