Boost C++ Libraries: Ticket #1041: Cygwin requires PATH setting.

Dave Abrahams — Fri, 08 Jun 2007 00:30:33 GMT

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 — Fri, 08 Jun 2007 00:46:14 GMT

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.

owner set

Dave Abrahams — Fri, 06 Jul 2007 01:24:27 GMT

owner set to Vladimir Prus

owner changed

René Rivera — Wed, 11 Jul 2007 19:50:57 GMT

owner changed from Vladimir Prus to René Rivera

v.haisman@… — Thu, 12 Jul 2007 11:20:33 GMT

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

status changed; resolution set

Vladimir Prus — Wed, 25 Mar 2009 07:33:12 GMT

status new → closed
resolution → wontfix

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.