Hi Stefan,
Stefan Bodewig <[EMAIL PROTECTED]> writes:
> On Mon, 15 Mar 2004, Arnaud Vandyck <[EMAIL PROTECTED]> wrote:
>
>> I'd like to make some changes in the
>> ant-1.6.1/src/main/org/apache/tools/ant/taskdefs/compilers/Gcj.java
>> task to change the behavior. I'd like ant NOT to pass the -C
>> argument if a nested <compilerarg> tag exists.
>
> This is hard to do in a backwards compatible way.
>
> Honestly, I'm not sure how big our gcj user base is and how many of
> them use <compilerarg> to pass additional arguments, the answer could
> very well be zero.
This is not a problem. I'll try to implement it myself and if the patch
is not good for you, maybe we'll apply it only in Debian. Maybe we'll
need it in a near future... we are not sure yet.
> But if it is bigger than that, such a change would break their builds.
Isn't possible in the Gcj class to know if there is a nested
<compilerarg> tag and look at the arguments of this tag?
> Is there a command line argument that you'd always use when compiling
> to native code, like --main? If this was the case, we could silently
> omit -C if compiler args have been specified and one of them started
> with --main=.
--main and maybe '-o', I don't know, but I'll ask on gcj mailing list.
> The only other solution I'd see would be a compiler specific magic
> property. Something like build.compiler.gcj.native and we'd drop -C
> if that property was set to true.
No problem for me if everything is well documented ;-) Seems to be a
good solution. Can you point me were I have to patch such a possibility
or will you do that? (I'm not in a hurry at all, it's a possible future
project! ;-) )
Many thanks for your time and help,
--
~/.signature not found
Packages should build-depend on what they should build-depend.
-- Santiago Vila on debian-devel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
