aYaFish / bullshtml

Automatically exported from code.google.com/p/bullshtml
0 stars 0 forks source link

Output always output absolute paths #18

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run a coverage using Bullseye 8.7.42 on Linux-x64
2. Parse xml output using: env PATH=$BULLSEYE_BIN:$PATH bullshtml/bullshtml 
bulls-html
3. Open the HTML using: google-chrome bulls-html/index.html

What is the expected output? What do you see instead?
The data is correct but I'm getting a lot of really long paths such as:
  /home/mattias/hg/dev/build/Debug-Bullseye/bin/iscsishared 0.0% 0.0%

After copying the coverage file to the base directory I get a shorter path:
  /home/mattias/hg/dev/iscsiinitiator 0.0% 0.0%

I've managed to reduce the covhtml output to a relative path using:
  $BULLSEYE_BIN/covhtml --srcdir . --tab 4 --file $COVFILE coverage-html
and this results in a much more readable path such as:
  iscsiinitiator/

What version of the product are you using? On what operating system?
Bullseye 8.7.42 on Linux-x64

Please provide any additional information below.
How can I configure bullshtml to output relative paths?

Thanks!
Mattias

Original issue reported on code.google.com by matt...@solidfire.com on 5 Feb 2013 at 10:04

GoogleCodeExporter commented 9 years ago
By considering this more, I can recall why I did like it.
The source code can be distributed in several drives and it really happens.
Relative path on the files distributed several drives are actually working.
Instead of using relative path, I'll replace the wrong path with symbol soon.

Original comment by junoy...@gmail.com on 18 Feb 2013 at 3:22