Boost logo

Boost-Build :

From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-06-26 09:57:35


[2003-06-26] Vladimir Prus wrote:

>Rene Rivera wrote:
>> [2003-06-25] Rene Rivera wrote:
>> >Stay tuned ;-)
>>
>> OK, rewrite of the print.text rule is done. AFAIK no outside changes are
>> needed. But the use in response-file should not need to use the "suffix"
>> workaround, but it won't hurt either.
>
>Thanks! But, unfortunately, not everything is quite right. When I run
>
> test_all.py borland
>
>on windows, the 'generator_test.py' fails, because print.text invokes
'escape'
>on empty string.

Hmm, shouldn't have happened :-( I'll fix ASAP...

>One more comment: I still don't understand 'prefix/suffix' thing. Do you
mean
>that 'prefix' text will be output before the target is created?

No. The output in the file will be prefix strings, followed by body strings,
followed by suffix strings. That allows for calling print.text in some order
other than first to last. Like the HTML output does, where it needs to set
up the "<html><body>..." and "...</body></html>" prefix and suffix.

>And what's
>"actual execution order of text rule"? I'm really lost on those
questions....

The order that the print.text is evaluated in Jam. For example if you do:

some-file-action-0 file.txt ; #:: echo 0
some-file-action-1 file.txt ; #:: echo 1
print.text file.txt : 2 ;
print.text file.txt : 3 ;

It will produce: 0, 1, 2, 3 lines. But if you do:

some-file-action-0 file.txt ; #:: echo 0
print.text file.txt : 2 ;
some-file-action-1 file.txt ; #:: echo 1
print.text file.txt : 3 ;

It will produce: 0, 2, 3, 1 lines. This is because it's the
evaluation/execution order of the actions on the target file that matter.
And the print.text rule now uses only 1 action.

I can try rewording the docs, but if the docs grow any larger they start
rivaling the size of the code itself ;-)

-- grafik - Don't Assume Anything
-- rrivera (at) acm.org - grafik (at) redshift-software.com
-- 102708583 (at) icq

 


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