ame boat and was only able to solve it through wrapping ant in a
> cmd script. Since I'm invoking Ant indirectly through a JAVA app it makes it
> hard to debug unless I use remote debugging (which is slightly painful). Have
> you been able to find a solution since your post?
&
2008/4/23 Steve Loughran <[EMAIL PROTECTED]>:
> Paul Richards wrote:
>
> > Hi,
> > I'm trying to use cpptasks-1.0b5 with Ant 1.7.0 on a C++ a project
> > that must be built with MSVC in both 32-bit and 64-bit flavours. With
> > MSVC this means we must buil
As my build.xml grows larger I'm sure this will cause pain when debugging.
So my question is how to specify the path to cl.exe neatly? Can the
path to cl.exe be specified manually to cctask? Does Ant support
calling itself in a neater way
