1 Use the filter_exes filter to generate a set of files listing the executables

     2 created in a build.  A separate file will be created for each layer name and

     3 each configuration containing executable files.  The filter can be run on an

     4 existing log file as follows:

     5 

     6 sbs_filter --filter=filter_exes < logfile

     7 where 'logfile' is the name of the logfile you want to analyse.

     8 

     9 By default it will create the files in the current directory, named

    10 '<layer>_<config>.txt' e.g. 'layerone_armv5_urel.txt'.  If layers are not in

    11 use (e.g. the build was not based on a system definition) the layer name used

    12 will be 'nolayer' - e.g. 'nolayer_armv5_udeb.txt'.

    13 

    14 The location for output files can be overridden using the 'output' argument.

    15 To limit its operation to specified layers or configs, the 'layer' and 'config'

    16 arguments can be supplied, multiple times if necessary:

    17 

    18 sbs_filter --filter=filter_exes[output=mydir,layer=layerone,layer=layertwo,config=armv5_urel] < logfile

    19 

    20 This will search for executables generated from either 'layerone' or 'layertwo'

    21 components which were also build for armv5_urel.  The filter will record an

    22 executable if it matches any of the layers specified and also was built for any

    23 of the configs specified.

    24 

    25 The files contain a list of filenames with no paths and no other information, 

    26 for example:

    27 

    28 HelloWorld.exe

    29 Dummy.exe

    30 epoc.exe

    31 [...]

    32 

    33 A file will only be produced if there are any filenames to go into it.  The

    34 filter will report on any files that have been created e.g:

    35 

    36 Wrote 242 file(s) into layerone_armv5_urel.txt

    37 Write 45 file(s) into layertwo_armv5_urel.txt

    38 

    39 Note that argument names may be abbreviated e.g.

    40 

    41 sbs_filter --filter=filter_exes[o=mydir,l=layerone,c=armv5_urel] < logfile

    42