Sorry for the delay.
Simon == Simon Richter [EMAIL PROTECTED] writes:
[...]
Simon The question is basically: Should jar files be treated
Simon as libraries, losing the ability to stuff application
Simon data into them, or should they be treated as
Simon to-be-implemented archives, which
Simon == Simon Richter [EMAIL PROTECTED] writes:
[...]
(*) I'm assuming _LIBRARIES and _LTLIBRARIES have been merged
first.
Simon ... since jars would be an exception then, since they
Simon are not built with libtool as all other libraries are.
Sorry, the plan is *not* to always use
Alexandre,
On Tue, Feb 04, 2003 at 08:00:07PM +0100, Alexandre Duret-Lutz wrote:
Simon == Simon Richter [EMAIL PROTECTED] writes:
[Archives as directories]
Simon ... Hrm, that would go in the direction of generic archive target
Simon support, and one would have to think about files in
Simon == Simon Richter [EMAIL PROTECTED] writes:
[...]
Simon Hrm, what if an archive would be treated like a directory, i.e.
Simon foo_jar_DATA = foo.properties
Sounds like a nice idea.
Simon ... Hrm, that would go in the direction of generic archive target
Simon support, and one would
Eric,
On Fri, Jan 31, 2003 at 11:19:29PM -0500, Eric Siegerman wrote:
foo_jar_JAVA = Foo.java
Don't forget that JARs can contain other things than .class
files; it'd be nice if there was an automakish way to say
include these other files too.
Hrm, what if an archive would be treated like
