Peter Graves said:
> On Tue, 3 Aug 2004 at 21:43:51 -0400, Larry Clapp wrote:
[my whining snipped]
> Let me make sure I understand what you're requesting.
> You'd like me to spend, say, an hour or so, minimum, investigating
> what options the jar command supports on all known versions of Java
> (an hour seems way short for that), or else spend an hour or two
> writing some custom Java code to emulate the jar command, plus time
> for testing, so you can save 9.5 seconds?
Well, no, so that everyone who builds j on a slower box could save
I-don't-know-how-many-seconds. Maybe a lot.
Some more cars in my alleged train of thought: I thought autoconfig might
already have an option for this (it seems to have one for everything
else), and you could just enable it. (Warning: I don't know autoconfig.)
Barring that, I thought you could just run a test jar with @list_of_files
during the configure process, and if it works, use it in the Makefile; if
not, build the jar in stages.
> How often do you build j.jar?
Several times a day, so far.
>> Or should I just stop whining? :)
> Do the math.
*grin* I have pondered the equations, and they reveal: I am impatient. I
Just so you know: the first part of the new jar command
jar cmf manifest ../j.jar Main.class org/armedbear/j/*.class
fails on AIX 5.1 with the same 'arglist too long' that Sam was getting
under Cygwin. AIX sucks.