> Hi,
> 
> Two things... 1)  Is this not already after the path?  Because I stuck it at 
> the end.
> 
> %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).

Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to