From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2008-06-26 20:33:00
Mat Marcus wrote:
> On Thu, Jun 26, 2008 at 4:17 PM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
>> the msvc.jam
>> commands where never intended, and never will be intended, to work in any
>> shell other than the CMD.EXE shell.
> I am surprised at the "never will be intended" part. We rely on using
> bjam with msvc compilers from the cygwin bash shell for years. Thread
> changes broke this in 1.35, but we are using the workarounds mentioned
> above to get things working again. Have I misunderstood your claim
> above? If not then, perhaps it is time for me to begin a search for a
> replacement build system.
It's a minor misunderstanding. In response to some problems the OP was
having in running msvc from a cygwin shell he responded with the bjam
commands as run from the cygwin shell. But those commands never  run
within the cygwin shell. The commands are written to a temporary BAT
file, and CMD.EXE is popen executed to run the .BAT file. That behavior
wont change. Hence any fixes that involve it running directly within the
cygwin shell are irrelevant.
 I think it's possible, with some hacking, to force it behave
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
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