On 8/10/07, David Ashley <dashley@...> wrote:
> I prefer to stay away from Cygwin. I get the feeling that most Microsoft
> programmers don't like/trust it. Or they just don't like the Unix-like
> environment it forces you to use. I think they would prefer tools that can
> be used from the standard Windows command shell. It is just not as intrusive
> to their development process as the Cygwin environment.
I didn't say anything when Rony brought up Cygwin, but you are right. The
problem with Cygwin is that you can not work in the Windows environment.
You have to work in a special Cygwin shell. Plus, all the tools have to run
through a translation layer.
The GnuWin32 tools are native Windows applications, as would be the
Microsoft Services for Unix tools.
If you want to use things like touch, gawk, sed, tar, etc., using the native
Windows versions of those tools is just a much better solution.
In my opinion, if you are building something that runs on Windows, you
simply can not beat the Microsoft compiler, linker, resource compiler, and
Platform SDK tools. You are foolish to try and get around that, you are
just beating your head against the wall for no purpose. As soon as you get
some tools that are comparable, Microsoft will change the playing field and
sweep the run out from under your feet. Now, I don't think that's right, or
ethical, or fair, but it is a reality.
However, the goal of having more portable build tasks is important. If we
can do that using tools like gawk, touch, diff, etc., then we can do that by
using the open source GnuWin32 or the Services for Unix.