[PATCH] covoar.cc: Correct build path checks for multiple executables.

[Vijay Kumar Banerjee]

hello,

I have attached the html report !
Well it looks good but I hardcoded the paths, at least that gave the proper
idea of what exactly needs to be done. Now I understand why
--rtems-builddir stayed there for a long time , it makes the job simple .

Here's a point that needs discussion :

1. the coverage.py in it's current state(before the updates I made today)
tries to parse the score-symbols.ini file (class symbols_configuration()) ,
which is not needed after the recent updates to covoar which makes it work
from covoar itself. I have just removed that class for now .

One thing can be done, which I think will solve parsing of the absolute
path of the library as well. It is to implement the the logic that Chris
used in covoar.cc , into the python script for coverage . Then we can do an
os.path.abspath() for the absolute path and the extract the directory name
from there for the html report from the same place. Can we do it that way ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180518/99e491b3/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2018-05-18 01-08-06.png
Type: image/png
Size: 62789 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180518/99e491b3/attachment-0002.png>