Eliminating hardcoded paths for coverage analysis

[Hermann Felbinger]

Dear all!

I'm currently working on a coverage report generator for RTEMS.
In the current version a user has to set the absolute paths to the
libraries, which are analyzed for coverage, in a config file, e.g., see [1].

A detailed explanation how to execute the test cases and how to invoke the
generation of coverage reports, can be found in [2].

To eliminate the absolute paths to the analyzed libraries from the config
file, I decided to add a command line parameter '--rtems-cpukit' which has
to be set by the user, and points to the cpukit directory within the built
rtems directory. An example for the usage of this parameter is:
--rtems-cpukit=/home/hf/development/rtems/b-leon2/sparc-rtems4.11/c/leon2/cpukit/
Now relative paths to the libraries can be used in the config file, as
shown in [3].

Do you think this is a useful solution to get rid of the absolute paths?
Could there be some libraries outside the cpukit directory that are
analyzed for coverage?

Best,
Hermann

[1]
https://github.com/hermann19829/rtems-tools/blob/master/tester/rtems/testing/coverage/symbolSets_pc386.config
[2]
http://socis2015rtems.blogspot.co.at/2015/07/build-rtems-and-execute-coverage.html
[3]
https://github.com/hermann19829/rtems-tools/blob/master/tester/rtems/testing/coverage/symbolSets.config
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20150804/da009992/attachment.html>