qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Meyering <...@meyering.net>
Subject Re: better bootstrap and gen/* dependencies
Date Sat, 02 Dec 2006 06:40:37 GMT
Alan Conway <aconway@redhat.com> wrote:
> Jim I had problems with this - where are $JAVA and $JAVAC supposed to be
> set? I've got to go, I'll apply the patch tomorrow unless Gordon beats
> me to it.


Those variables are set via configure.  The AC_CHECK_PROGS autoconf macro
AC_SUBST's them.  I've verified that the patch applies to a tree with no
modifications and that a subsequent "make" reruns autoconf, configure et
al (checking for java and javac) and rebuilds all of the required pieces.

What symptoms do you have?

> On Fri, 2006-12-01 at 21:32 +0100, Jim Meyering wrote:
>> This changes gives qpid improved dependency tracking: Now, if someone
>> modifies one of the gentools/... .java or .tmpl files, the source files
>> in gen/ will be regenerated.  But only if java and javac are available
>> and this is not a stand-alone qpid-cpp directory.
>> Also with this change, you should be able to "svn remove" the
>> generated file, gen/gen-src.mk, since the modified bootstrap
>> script generates it up front.
>> 2006-12-01  Jim Meyering  <meyering@redhat.com>
>> 	* configure.ac: Use an automake conditional to indicate when we
>> 	have access to files outside of the current hierarchy, and when
>> 	we have the tools (java and javac) to build some generated files.
>> 	* gen/Makefile.am: Don't use $(abs_srcdir); not needed.
>> 	(timestamp): Depend on java sources and C++ template files,
>> 	if we're building in a qpid tree.
>> 	Use $(JAVA) and $(JAVAC), rather than hard-coding those names.
>> 	(gen-src.mk) [$(java_sources), $(cxx_templates)]: New rules to
>> 	generate these lists of file names.
>> 	* bootstrap: Also generate gen/gen-src.mk.
>> 	But do that only if we're in a qpid hierarchy.
>> 	Redirect make's stdout to /dev/null.

View raw message