You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by David Corbin <dc...@machturtle.com> on 2000/12/28 23:39:22 UTC
oddity
<copy todir="foo">
<fileset dir="bar">
<include name="./foobar"/>
</fileset>
</copy>
Doesn't copy anything. But, if I remove the leading "./" it will copy
it.
--
David Corbin
Mach Turtle Technologies, Inc.
http://www.machturtle.com
dcorbin@machturtle.com
Re: IDL compilation with ant -> problem?
Posted by G Ramasubramani <gr...@aztec.soft.net>.
I suppose instead of calling execon, you will have to write your own
task which shall internally generate the dependancies and check the
time-stamps to decide which idl to compile and which not to.
Have a look at the Javac.java class. It might help you.
Rama
Barry Nauta wrote:
> Hello,
>
> We want to use ant for our build-process but encountered the following
> problem:
>
> We use quite a lot of IDLs and compilation of all IDLs together takes
> more than 15
> minutes.
>
> The following works just fine in ant
>
> 36 <target name="idl" depends="init">
> 37 <execon
> 38 executable="idl2java"
> 39 >
> 40 <arg line="-gen_included_files -examples
> -retain_comments -boa -root_dir ${idl-javafiles} -I ${idl-src}" />
> 41 <fileset dir="${idl-src}">
> 42 <include name="**/*.idl" />
> 43 </fileset>
> 44 </execon>
> 45 </target>
>
> The problem with this target is that it compiles ALL idl files (so
> taking more that 15 minutes to compile), where we would like to compile
> only those who have changed or those who are influenced by a change
> (dependencies).
>
> Is there some sort of dependency checking possible or do we have to
> write a seperate tool that generates build files based on dependencies?
>
> Thanks,
> Barry
Re: IDL compilation with ant -> problem?
Posted by Mikael St�ldal <mi...@staldal.nu>.
In article <ND...@ebinteractive.com.au>,
"Conor MacNeill" <co...@ebinteractive.com.au> wrote:
>Have you looked at the uptodate task?
Yes, and I'm currently using it. But it's not an elegant solution.
RE: IDL compilation with ant -> problem?
Posted by Conor MacNeill <co...@ebinteractive.com.au>.
Mikael,
Have you looked at the uptodate task?
Conor
> -----Original Message-----
> From: Mikael Ståldal [mailto:mikael@ingen.reklam.staldal.nu]
> Sent: Wednesday, 3 January 2001 1:53
> To: ant-user@jakarta.apache.org
> Subject: Re: IDL compilation with ant -> problem?
>
>
> In article <B6...@x180.net>,
> James Duncan Davidson <du...@x180.net> wrote:
>
> >> Is there some sort of dependency checking possible or do we have to
> >> write a seperate tool that generates build files based on dependencies?
> >
> >Dependency checking is a function of the task itself.
>
> Then I want to have general dependency checking in the <java>, <exec>
> and <execon> tasks, since they are used to invoke translation utilites.
>
> I don't like the idea to have to write a separate task for each
> translation utility, just because I want basic dependency checking.
>
> For the <java>, <exec> and <execon> tasks, you should be able to
> specify one target file and a Fileset of source files, and the task
> should only be executed if at least one of the source files is newer
> than the target file. For <execon>, you already have the source file
> set.
>
Re: IDL compilation with ant -> problem?
Posted by Mikael St�ldal <mi...@ingen.reklam.staldal.nu>.
In article <B6...@x180.net>,
James Duncan Davidson <du...@x180.net> wrote:
>> Is there some sort of dependency checking possible or do we have to
>> write a seperate tool that generates build files based on dependencies?
>
>Dependency checking is a function of the task itself.
Then I want to have general dependency checking in the <java>, <exec>
and <execon> tasks, since they are used to invoke translation utilites.
I don't like the idea to have to write a separate task for each
translation utility, just because I want basic dependency checking.
For the <java>, <exec> and <execon> tasks, you should be able to
specify one target file and a Fileset of source files, and the task
should only be executed if at least one of the source files is newer
than the target file. For <execon>, you already have the source file
set.
Re: IDL compilation with ant -> problem?
Posted by James Duncan Davidson <du...@x180.net>.
On 12/29/00 2:19 AM, "Barry Nauta" <ba...@swITch.be> wrote:
> Is there some sort of dependency checking possible or do we have to
> write a seperate tool that generates build files based on dependencies?
Dependency checking is a function of the task itself. So in the Javac case,
there are some fairly good, though not thorough, checks based on timestamps
to determine what needs to be recompiled. Such functionality is probably
what is needed in your task (though I've got to admit, I haven't looked at
the IDL task).
.duncan
--
James Duncan Davidson duncan@x180.net
!try; do()
IDL compilation with ant -> problem?
Posted by Barry Nauta <ba...@swITch.be>.
Hello,
We want to use ant for our build-process but encountered the following
problem:
We use quite a lot of IDLs and compilation of all IDLs together takes
more than 15
minutes.
The following works just fine in ant
36 <target name="idl" depends="init">
37 <execon
38 executable="idl2java"
39 >
40 <arg line="-gen_included_files -examples
-retain_comments -boa -root_dir ${idl-javafiles} -I ${idl-src}" />
41 <fileset dir="${idl-src}">
42 <include name="**/*.idl" />
43 </fileset>
44 </execon>
45 </target>
The problem with this target is that it compiles ALL idl files (so
taking more that 15 minutes to compile), where we would like to compile
only those who have changed or those who are influenced by a change
(dependencies).
Is there some sort of dependency checking possible or do we have to
write a seperate tool that generates build files based on dependencies?
Thanks,
Barry