RE: Don't see any output to stdout from commands

[William Sheehan]

> Really?  I use VS 6 sometimes, and the feature is still 
> there.  What version dropped it?

It was dropped in VS7 (.NET).  The new paradigm is to use devenv.exe by
passing it a solution file and a "configuration" (e.g. Debug or Release).

Unfortunately I'm not familiar with actually using devenv; just contributing
an answer to your question :)

William Sheehan
Builds Engineer / Network Administrator
Open Interface North America

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> .org] On Behalf Of Eli Zaretskii
> Sent: Friday, September 08, 2006 9:28 AM
> To: Krzysztof Nosek
> Cc: address@hidden; address@hidden
> Subject: Re: Don't see any output to stdout from commands
> 
> 
> > Date: Fri, 08 Sep 2006 10:34:46 +0200
> > From: Krzysztof Nosek <address@hidden>
> > Cc: address@hidden
> > 
> > of course calling cl.exe, link.exe and all the stuff 
> directly _is_ an 
> > option. But, sometimes, when you use such tool as Visual 
> Studio, you 
> > want to have projects (.vcproj) and solution files (.sln) 
> configured 
> > so that you can build-on-request during development from inside the 
> > VS's IDE (or your boss wants, or your fellow developer does, ...).
> > 
> > So, these VS files contain (mostly) all information 
> concerning build 
> > issues of given solution. But it's only devenv who knows 
> how to deal 
> > with it.
> 
> Okay, but then why invoke devenv from Make?
> 
> > BTW, Previous versions of VS used to have feature of generating 
> > makefile (nmakish one) given solution file. But that feature 
> > disappeared many years ago...
> 
> 
> 
> _______________________________________________
> Make-w32 mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/make-w32
>