Re: [jamboost] Re: First cut at a SHELL command for bjam

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2005-06-24 10:25:37

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:

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.

2. For testers that have the bjam built automatically and only have a 
compiler which doesn't have popen.

By the way, by "minimally detect" I meant that we have 
OPT_SHELL_BUILTIN, or such, as we have for some other extensions that we 
can toggle in the build.jam.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - Grafik/jabber.org