Cygwin requires PATH setting.

[René Rivera]

It turns out when one uses Cygwin GCC it requires that the bin directory be in the PATH for it to execute commands correctly. Without bin in the PATH one gets noops. This would not be a problem if one is running from the Cygwin Bash shell. But if one runs from say the Windows CMD shell, and hasn't set the PATH, nothing works. Like the msvc toolset, we can enforce the correct behavior by setting the PATH when running the gcc actions for the cygwin case.

[Dave Abrahams]

Probably we should get the PATH from the windows registry. I don't know all the details of where to look, but if you check out tools/build/v2/tools/python.jam and look for "Cygnus Solutions" you'll see a place where we look for registry values related to Cygwin. You can surely divine the precise answers by looking at your own registry. Use (and factor out) the "software-registry-value" rule from python.jam so you find the right stuff even on 64-bit systems.

[René Rivera]

Thanks Dave... I looked and the most modular solution I can see is to abstract out the cygwin-to-windows-path rule, and hence also the one you mention. And then call it with "/usr/bin", adding the result to the PATH. Perhaps moving the rule to path.jam, or os.jam.

[v.haisman@…]

FWIW, I think that using Cygwin tools outside Cygwin shell is not worth supporting.

[Vladimir Prus]

It does not seem that any new users run into this problem, and using cygwin tools outside cygwin shell is rare, and it is gcc problem, and it could be that current versions of gcc no longer have this problem, so I'm gonna declare this is not something to be fixed in Boost.Build.