It sounds like you want to use MinGW (http://www.mingw.org/) rather
than Cygwin. When used in conjunction with the MSYS shell
environment, MinGW allows building normal WIN32 applications with no
dependence on anything but standard WIN32 DLLs.
Bob
On Fri, 9 Dec 2005, BRM wrote:
I want to be able to run the AutoTool chain natively
under Windows. I did some looking around, and
everyone´s answer primarily seems to be ¨run Cygwin¨.
Unfortunately, Cygwin is not an option for me as I
can´t tell my clients to install Cygwin to use my
product. (They´d go to someone else.) Same applies for
Microsoft´s SFU, and UWin.
It would be nice to use those environments except that
the problem is they introduce dependancies due to the
environment. I want to run the tool chain natively in
Windows so that I don´t have to maintain a VC++ setup
in addition to my Unix tool chain. (And I´d rather
avoid the batch files and other stuff as well.)
Does anyone know of a project that could help solve
the problem? I guess, I am primarily looking for a
non-intrusive cmd.exe replacement for Windows 2000
Pro.
TIA,
Ben
======================================
Bob Friesenhahn
bfriesen@xxxxxxxxxxxxxxxxxxx, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
