[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: automake/514: check_JAVA files are always compiled
From: |
Ralf Wildenhues |
Subject: |
Re: automake/514: check_JAVA files are always compiled |
Date: |
Wed, 10 Jan 2007 19:35:35 +0100 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
Hello,
* Roberto Bagnara wrote on Fri, Dec 22, 2006 at 03:17:21PM CET:
>
> The subject says all. Is there any workaround?
> check_JAVA files are always compiled, not only in case of `make check'.
Quoting 'info Automake Java':
| Any `.java' files listed in a `_JAVA' variable will be compiled with
| `JAVAC' at build time. By default, `.java' files are not included in
| the distribution, you should use the `dist_' prefix to distribute them.
[...]
| Currently Automake enforces the restriction that only one `_JAVA'
| primary can be used in a given `Makefile.am'. The reason for this
| restriction is that, in general, it isn't possible to know which
| `.class' files were generated from which `.java' files, so it would be
| impossible to know which files to install where. For instance, a
| `.java' file can define multiple classes; the resulting `.class' file
| names cannot be predicted without parsing the `.java' file.
Seems it's working as documented, no?
No, I don't know why this limitation exists, or what would be needed to
lift it. I don't know Automake's java support very well.
Hope that helps.
Cheers,
Ralf
- Re: automake/514: check_JAVA files are always compiled,
Ralf Wildenhues <=