On Thu, May 29, 2008 at 3:51 AM, Paul Richards <[EMAIL PROTECTED]> wrote:
> I'm afraid I was only evaluating ant+cpptask (as well as other tools)
> in order to find the best tool for my project. Unfortunately
> ant+cpptask didn't win, and so I didn't spend any more time on it.
Care to share a bit
manually to cctask? Does Ant support
>> calling itself in a neater way that doesn't require spawning a new
>> shell?
>>
>>
>>
>> --
>> Paul Richards
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
> Quoted from:
> http://www.nabble.com/Setting-path-to-MSVC-compiler-with-cctask-tp16853547p16853547.html
>
>
--
Paul Richards
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Wed, Apr 23, 2008 at 5:55 AM, Paul Richards <[EMAIL PROTECTED]> wrote:
> So my question is how to specify the path to cl.exe neatly? Can the
> path to cl.exe be specified manually to cctask?
Not that I remember.
> Does Ant support calling itself in a neater way that
> doesn't require spawn
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 build the project with two different versions
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 build the project with two different versions
of "cl.exe".
I can't put both on my PATH, and so I'd like to sp
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 build the project with two different versions
of "cl.exe".
I can't put both on my PATH, and so I'd like to specify in my Ant
build s
