This is true, but only the Ant output, not the VC++.NET output. It seems that when Ant
executes the build, the VC++.NET output is redirected somewhere, or perhaps does not
know where to go. The output I'm talking about is the stuff that Visual Studio
compiler (and linker) outputs to describe what
happened in the build. Here is a basic example:
------ Build started: Project: agents, Configuration: Debug Win32 ------
agents - up-to-date.
Build Time 0:00
------ Build started: Project: calc, Configuration: Debug Win32 ------
calc - up-to-date.
Build Time 0:00
------ Build started: Project: comm, Configuration: Debug Win32 ------
comm - up-to-date.
Build Time 0:00
...
---------------------- Done ----------------------
Build: 17 succeeded, 0 failed, 0 skipped
When I type into the commandline devenv ../../Omm.sln /build debug /project
WhatIfEngine, the output comes out to the cmd window. But when Ant executes the exact
same command, it does not appear.
Jeff
-----Original Message-----
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Friday, April 02, 2004 2:52 PM
To: 'Ant Users List'
Subject: RE: Newbie; Sending VC++.NET build output to cmd window
The output of <exec> goes to the console that started Ant by default. --DD
> -----Original Message-----
> From: White, Jeffrey [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 02, 2004 1:45 PM
> To: 'Ant Users List'
> Subject: RE: Newbie; Sending VC++.NET build output to cmd window
>
> Thanks for the response!
>
> Both those tasks take filenames as arguments, so I could see how they
> would be used to direct output to a file. But what about to the cmd
> window?
>
> Thanks,
> Jeff
>
> -----Original Message-----
> From: Dominique Devienne [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 02, 2004 2:36 PM
> To: 'Ant Users List'
> Subject: RE: Newbie; Sending VC++.NET build output to cmd window
>
>
> Check out <exec>'s output attribute, or the <record> task. --DD
>
> > -----Original Message-----
> > From: White, Jeffrey [mailto:[EMAIL PROTECTED]
> > Sent: Friday, April 02, 2004 1:00 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: Newbie; Sending VC++.NET build output to cmd window
> >
> > Hello,
> >
> > I'm using the exec task to run devenv.exe to build MS Visual C++
> solutions
> > and projects. I would like the output messages of these builds to go to
> a
> > file AND to the cmd window from which the ant target was called. Is this
> > possible, and if so, how?
> >
> > Here's what I'm doing now, which only outputs to the specified file and
> > does not appear in the cmd window:
> >
> > <exec dir='.' executable='devenv'>
> > <arg line='../../Solution.sln /build debug /project
> > ${ant.project.name} /out ${output.dir}/${ant.project.name}_log.txt' />
> > </exec>
> >
> > If I use the following (with the "/out ..." argument omitted) the ouput
> > still does not appear in the cmd window:
> >
> > <exec dir='.' executable='devenv'>
> > <arg line='../../Solution.sln /build debug /project
> > ${ant.project.name}' />
> > </exec>
> >
> > However, if I manually type the command that the above code generates,
> the
> > output is directed to the cmd window.
> >
> > So, to quickly restate the question: How do I get build output to the
> cmd
> > window AND to a file?
> >
> > Thanks in advance,
> >
> > Jeff White
> >
> >
> >
> > DISCLAIMER
> > This e-mail, and any attachments thereto, is intended only for use by
> the
> > addressee(s) named herein and may contain legally privileged and/or
> > confidential information. If you are not the intended recipient of this
> e-
> > mail, you are hereby notified that any dissemination, distribution or
> > copying of
> > this e-mail, and any attachments thereto, is strictly prohibited. If you
> > have received this e-mail in error, please immediately notify me and
> > permanently delete the original and any copy of any e-mail and any
> > printout thereof.
> > E-mail transmission cannot be guaranteed to be secure or error-free.
> The
> > sender therefore does not accept liability for any errors or omissions
> in
> > the contents of this message which arise as a result of e-mail
> > transmission.
> > NOTICE REGARDING PRIVACY AND CONFIDENTIALITY
> > Knight Trading Group may, at its discretion, monitor and review the
> > content of all e-mail communications.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DISCLAIMER
This e-mail, and any attachments thereto, is intended only for use by the addressee(s)
named herein and may contain legally privileged and/or confidential information. If
you are not the intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution or copying of
this e-mail, and any attachments thereto, is strictly prohibited. If you have received
this e-mail in error, please immediately notify me and permanently delete the original
and any copy of any e-mail and any printout thereof.
E-mail transmission cannot be guaranteed to be secure or error-free. The sender
therefore does not accept liability for any errors or omissions in the contents of
this message which arise as a result of e-mail transmission.
NOTICE REGARDING PRIVACY AND CONFIDENTIALITY
Knight Trading Group may, at its discretion, monitor and review the content of all
e-mail communications.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
