This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
RE: Shallow package and Java
- To: "'Allan Clark'" <allanc at sco dot com>
- Subject: RE: Shallow package and Java
- From: Ken N Linton <klinton at gte dot net>
- Date: Fri, 31 Mar 2000 17:50:07 -0800
- Cc: "'automake at gnu dot org'" <automake at gnu dot org>
- Encoding: 49 TEXT
Allan,
Thanks for the reply. Seems that when using automake and autoconf,
the following lines are inserted in the Makefiel generated by configure:
JAVAC = javac
JAVAROOT = $(top_builddir)
$(JAVAC) -d $(JAVAROOT) $(JAVACFLAGS) $?
So the .class files always end up in the top-level build directory! Any
ideas how one can over-ride this behaviour using autoconf/automake?
Yes, I'd looked at the output of javac -verbose as a posibilty for auto
generating dependencies between java source files. Can't say I fancy
parsing the output of this. I was hoping for something like "cc -M foo.c"
Ken
-----Original Message-----
From: Allan Clark [SMTP:allanc@sco.com]
Sent: Friday, March 31, 2000 1:39 PM
To: Ken N Linton
Subject: Re: Shallow package and Java
Ken N Linton wrote:
>
> Hi,
>
> Two java-related questions on using automake/autoconf:
>
> 1. How can one control where javac puts the .class files?
I think it is
javac -d /my/dest/class/dir ... dog.java
... should create a /my/dest/class/dir/dog.class
> 2. How can one use automake to generate java depencies automatically?
You might get some kind of makedep capability through parsing the output
of "javac -verbose"
qv: http://uw7doc.sco.com/cgi-bin/man/man?javac+1dkjava
Allan Clark
SCO Professional Services
Murray Hill, NJ