>> %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program >> Files (x86)\ATI >> Technologies\ATI.ACE\Core-Static;C:\strawberry\perl\bin;c:\windows\batfiles;c:\mingw\bin;C:\Program >> Files (x86)\QT >> Lite\QTSystem;C:\utils\console2;C:\utils\win-bash;C:\utils;C:\lame;C:\gnuwin32\bin > > After the _C compiler_ tools. > > There is no C compiler tools in your PATH besides > cygwin, so cygwin is detected and tried to be used. > >> 2) I don't really believe it is cygwin, or does it rely on any cygwin DLLs. >> It's sourceforge page boasts: GnuWin provides Win32-versions of GNU tools, >> or tools with a similar open source licence. The ports are native ports, >> that is they rely only on libraries provided with any 32-bits MS-Windows >> operating system, such as MS-Windows 95 / 98 / 2000 / NT / XP / >> >> Nor does it have *cygwin*.* files anywhere in there.... > > cygstart.exe is used for cygwin detection. > > There is no problem in having cygwin tools in PATH, > for some targets it's even a requirement (mingwarm).
I have to correct this e-mail of mine. Cygwin _may_ cause harm when included with some other compiler tools, so if someone wants to keep Cygwin in PATH all the time, it's recommended to delete or rename cygstart.exe in cygwin bin dir, if it's not a goal to create cygwin Harbour builds, or compiler autodetection should be manually overridden using HB_COMPILER envvar (this is one the rare occasions). Even though for 99.99% of users, it's better to delete/rename cygstart.exe. Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
