Re: [Boost-build] [future] Implementation language(s)..

Subject: Re: [Boost-build] [future] Implementation language(s)..
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2016-10-26 13:35:08

On 26.10.2016 13:28, Chambers, Matthew wrote:
>
> On 10/26/2016 11:57 AM, Stefan Seefeld wrote:
>> On 26.10.2016 10:42, aaron_at_[hidden] wrote:
>>> Before we switched our products over to Boost.Build, there was
>>> an in-house build system written in Perl. It worked just fine when the
>>> projects were small, but as they grew, new "features" needed to be
>>> added to
>>> the build system in order to support the product.
>> It would really be great to have a place to collect such features
>> (actually "requirements" would be more appropriate in this discussion, I
>> suppose), so any new effort has some metric to measure its success
>> against.
> I agree. Perhaps Rene's Trello post would be suitable. Basically, I
> have many use cases from my own project which feel more like "data"
> than "logic" even though they contain a whole lot of logic (if
> <toolset>msvc in $(properties) { <foo>bar <baz>boo ; }) . But I could
> be doing it all wrong. ;)
>
> What about actions that make little files:
>
> # create a VERSION file which can be used by TC to parse the canonical
> pwiz version
> make VERSION : : @make_VERSION : <location>$(PWIZ_BUILD_PATH) ;
> actions make_VERSION { @($(STDOUT):E=$(version-tag:]=.)) > "$(<)" }
>
> ^- I hope this syntax can be much clearer in b3

I suggest we use the Boost.Build wiki to collect use-cases and other
artifacts. (To that effect I have just started
https://github.com/boostorg/build/wiki/Use-cases-and-Requirements).
Let's hope this will be useful...

        Stefan

-- 
      ...ich hab' noch einen Koffer in Berlin...