From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-07-12 11:22:46
Rene Rivera wrote:
> Vladimir Prus wrote:
>> We have a ticket in Boost Trac about need to set
>> PATH when using cygwin gcc:
>> Unfortunately, cygwin is already at the bottom of my
>> list of important toolsets, and using cygwin gcc from
>> cmd.exe makes it even worse.
>> So, it's not likely I'll get to this issue in the nearest 10 years.
>> Anybody wants to adopt the issue, or should I wontfix it?
> I assigned it to myself,
> but here's the more general plea/explanation on
> why fixing this is important... It's not really a problem for Cygwin
> only. In general the gcc toolset, and most others, don't do what the
> msvc and other Windows toolsets of doing precommand setup. It's a
> general pattern that it seems to me should be handled generically like
> the CONFIG_COMMAND var. Regardless... I'm fine with doing this myself ;-)
Why do you think it's necessary? With msvc, there's that vcvars script,
whereas with gcc, it was not required so far.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk