This is the mail archive of the java-discuss@sources.redhat.com mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: where should the .o files end up?


On Tue, 18 Jul 2000, Anthony Green wrote:

> 
> 
> On Tuesday, July 18, 2000 6:33 AM, Jeff Sparkes 
> [SMTP:jsparkes@internetivity.com] wrote:
> > I end with tooltip.o and com/internetivity/widget/tooltip.d
> 
> That's right.  The object file ends up in the current working directory by 
> default.  Of course, you can always use `-o 
> com/internetivity/widget/tooltip.o'.
> 
> I've often thought it would be convenient to have an option for the object 
> files to end up in a hierarchy mirroring the package hierarchy.  That would 
> be convenient when you really wish you could safely run `find ./ -name 
> \*.class -print | xargs gcj -O2 -c'.
> 
> AG

I am ok with using "gcj -c -o build/foo.o foo.java" for one file,
but what if you want to compile more than one .java file?
With javac, you can run "javac -d build *.java", it is really handy.

Mo DeJong
Red Hat Inc

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]