18
|
1 |
|
|
2 |
It is now possible to pass parameters from the command line into log filters.
|
|
3 |
This works in the same way for both sbs and sbs_filter commands.
|
|
4 |
|
|
5 |
For example:
|
|
6 |
|
|
7 |
sbs --filters=Foo[param1,param2,param3]
|
|
8 |
|
|
9 |
sbs_filter --filters=Bar[value] < build.log
|
|
10 |
|
|
11 |
|
|
12 |
Multiple filters with parameters can be specified if needed,
|
|
13 |
|
|
14 |
sbs --filters=Foo[param1,param2,param3],Bar[value]
|
|
15 |
|
|
16 |
|
|
17 |
In the 2.13.0 release there are two filters which take parameters:
|
|
18 |
|
|
19 |
1. sbs_filter --filters=FilterComp[wizard/group] < log
|
|
20 |
|
|
21 |
Here the parameter is (part of) a bld.inf path and the filter only prints
|
|
22 |
parts of the log which are attributable to the matching component. In the
|
|
23 |
example above, the log elements from any bld.inf which has "wizard/group"
|
|
24 |
as part of its path will be printed: normally, passing the full path name
|
|
25 |
will guarantee that only one component matches.
|
|
26 |
|
|
27 |
2. sbs_filter --filters=FilterTagCounter[info,recipe] < log
|
|
28 |
|
|
29 |
Here the parameters are a list of the element names to count. This is a
|
|
30 |
simple analysis filter that shows you how many instances of XMl elements
|
|
31 |
are in a log and how many characters of body text they have. |