ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From G Ramasubramani <gr...@aztec.soft.net>
Subject Re: IDL compilation with ant -> problem?
Date Thu, 28 Dec 2000 10:36:02 GMT
    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


Mime
View raw message