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

[Krzysztof Nosek]

Eli Zaretskii wrote: Okay, but then why invoke devenv from Make? Hmm, I don't quite follow. Suppose I have large heterogenous project (I do have), which I want to build with make, due to its numerous features and abilities. However, the project includes several solutions being developped and built under VS. So your project includes some parts that are built using Make techniques, and other parts that are built using Studio project files, is that right? Exactly. It contains of several VS projects plus a bulk of other staff. It shouldn't be hard to imagine that, I think. For production projects, there're usually some setup to be built, some help to be compiled, some docs to be generated, there's often some data to do something with etc. If so, I guess it makes sense to invoke devenv from Make, but it's quite an unusual setup, I'd say. Normally, if you use Make, you use it for building everything. I _do_ use Make for building everything. Just I invoke devenv for VS projects compilation and build. Is it really so unusual? I didn't manage to think up anything better than that :-)

_______________________________________________
Make-w32 mailing list
Make-w32@gnu.org
http://lists.gnu.org/mailman/listinfo/make-w32