Re: First cut at a SHELL command for bjam

From: David Abrahams (dave_at_[hidden])
Date: 2005-06-24 14:19:27

Rene Rivera <grafik.list_at_[hidden]> writes:

> David Abrahams wrote:
>> Rene Rivera <grafik.list_at_[hidden]> writes:
>> 
>>>Vladimir Prus wrote:
>>>
>>>>On Sunday 19 June 2005 23:36, Rene Rivera wrote:
>>>>
>>>>>Also the builtin doesn't compile when "popen" is not available in the
>>>>>runtime library, for example in the case of the MSL. 
>>>>
>>>>Much as I'd like jam_src to be fully portable, if adding a sufficient number 
>>>>of underscores to "popen" does not make it works with MSL, then I'd vote
>>>>to get this feature in, even if that breaks building with CW. This is much 
>>>>requested feature.
>>>
>>>I don't disagree ;-) Just that it should minimally detect when popen is 
>>>not available and remove the feature so that it compiles (and possibly 
>>>warn about it).
>> 
>> Why? For people using older BB?
>
> I'm not sure I understand what you mean by "older BB", but my
> reasons are:

A Boost.Build that isn't yet using the new SHELL feature.

> 1. For people who only have access to a compiler which doesn't have 
> popen and we don't have a prebuilt bjam available. They will follow the 
> instructions and try to compile it, and fail. Not a good way to get started.

But if Boost.Build is using SHELL, the failure to compile bjam is just
the first of a long string of problems, no?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com