ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Devienne" <DDevie...@lgc.com>
Subject RE: repository
Date Tue, 16 Nov 2004 17:31:13 GMT
> From: Russell Gold [mailto:russgold@gmail.com]
> 
> On Tue, 16 Nov 2004 09:06:24 -0600, Dominique Devienne
> <ddevienne@lgc.com> wrote:
> > Additionally, if the notion of what is a dependency could be
abstracted
> > a bit, it would be great. I'm not sure it's reasonable to ask for
this
> > now, but I'm throwing that it now so whatever design decision is
made
> > does not preclude it in the future. What I have in mind are zip
> > dependencies containing jar+native-libs+descriptors+etc... We're in
a
> > mixed Java-C/C++ environment, and some dependencies are in fact C++
> > libraries which export their public headers, import libs, and
runtime
> > .dll/.so as a zip.
> 
> Could you explain this further? Do you mean extracting things from zip
> files? Or is downloading them sufficient?

The C/C++ compiler won't like a jar:file://.../acme.zip!/acme/include
URL in the include path, so yeah, extracting will need to happen. I'm
not proposing <dependencies> or <getlibrary> to implement it, but to
provide some kind of hook to allow it. I already do these things in my
ad-hoc Ant extensions, but being able to replace my code with a more
Ant-based solution would be a better long term plan (easier to maintain
for my successors ;-).

Like I said, I'm not asking for it, just that it's considered in the
design, even if just to be rejected on the terms of "we won't do that,
we only care about pure Java"... --DD

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message