Brian Jones wrote:
>
> "Ian D. Stewart" <[EMAIL PROTECTED]> writes:
>
> > FYI, I'm working on a new build scenario, where each class is compiled
> > individually, ordered based on dependencies.
>
> I'm sorry, I don't see how this is any different compared to kjc or
> jikes which do the dependency ordering for you given any simple list
> of class files. Turn on the verbose flag for jikes to see if it is
> doing something while it is "locked up" in lib/Makefile.am.
The problem isn't with dependencies per se (and I can certainly see the
wisdom in automating the dependency checking process).
Rather, it is one of system resources. Using the "en mass" method, the
compiler attempts to compile all the classes of the classpath library at
once, and doesn't stop until it is done, or until it consumes enough
memory to degrade the systems performance enough to require a cold boot
(normally the latter)
On a relatively modern system, this is probably not much of an issue.
However, as I mentioned in passing in my previous e-mail, I am running
an older system. Specifically:
Processor: 75MHz Pentium
Memory: 16 MB Physical; 64 MB swap
Hard Drive: 1.2 GB WD Caviar w/ ~150 MB free
By compiling each class individually, the compiler compiles that single
class, along with any immediate dependencies, then stops, releasing
allocating resources. This results in a both a much cleaner and faster
(or, in my case, achievable) build process.
Regards,
Ian
