Joe Buck wrote:
That wouldn't have saved me in the case described above, as the pathnames
are already set in the executable. A *runtime* way of altering the
locations of the .gcda files would be nice to have. For example, we could
have something like
GCDA_PATH_PREFIX
which, if set, would be prepe
Joe Buck <[EMAIL PROTECTED]> writes:
| On Fri, Mar 25, 2005 at 08:03:55PM +0100, Gabriel Dos Reis wrote:
| > Joe Buck <[EMAIL PROTECTED]> writes:
| > | That wouldn't have saved me in the case described above, as the pathnames
| > | are already set in the executable. A *runtime* way of altering th
On Fri, Mar 25, 2005 at 08:03:55PM +0100, Gabriel Dos Reis wrote:
> Joe Buck <[EMAIL PROTECTED]> writes:
> | That wouldn't have saved me in the case described above, as the pathnames
> | are already set in the executable. A *runtime* way of altering the
> | locations of the .gcda files would be ni
Joe Buck <[EMAIL PROTECTED]> writes:
| Mark Mitchell <[EMAIL PROTECTED]> writes:
| > | When we generate data for feedback, we insert the .gcda name into the
| > | object file as an absolute path. As a result, when we try to do
| > | remote testing, we lose, as, in general the remote file system d
On Mar 25, 2005, at 9:47 AM, Gabriel Dos Reis wrote:
"Timothy J.Wood" <[EMAIL PROTECTED]> writes:
|A compiler option to set the target directory for these files (and
| the coverage ones!) would be great. Possibly even better would be an
| environment variable. If the user wants to compare two
"Timothy J.Wood" <[EMAIL PROTECTED]> writes:
| On Mar 24, 2005, at 11:59 PM, Mark Mitchell wrote:
|
| > When we generate data for feedback, we insert the .gcda name into
| > the object file as an absolute path. As a result, when we try to do
| > remote testing, we lose, as, in general the remote
Mark Mitchell <[EMAIL PROTECTED]> writes:
> | When we generate data for feedback, we insert the .gcda name into the
> | object file as an absolute path. As a result, when we try to do
> | remote testing, we lose, as, in general the remote file system does
> | not have the same file hierarchy as t
On Mar 24, 2005, at 11:59 PM, Mark Mitchell wrote:
When we generate data for feedback, we insert the .gcda name into the
object file as an absolute path. As a result, when we try to do
remote testing, we lose, as, in general the remote file system does
not have the same file hierarchy as the bu
On Thu, Mar 24, 2005 at 11:59:55PM -0800, Mark Mitchell wrote:
> When we generate data for feedback, we insert the .gcda name into the
> object file as an absolute path. As a result, when we try to do remote
> testing, we lose, as, in general the remote file system does not have
> the same file
Mark Mitchell <[EMAIL PROTECTED]> writes:
| When we generate data for feedback, we insert the .gcda name into the
| object file as an absolute path. As a result, when we try to do
| remote testing, we lose, as, in general the remote file system does
| not have the same file hierarchy as the build
When we generate data for feedback, we insert the .gcda name into the
object file as an absolute path. As a result, when we try to do remote
testing, we lose, as, in general the remote file system does not have
the same file hierarchy as the build system.
I understand why we generate an asbolu
11 matches
Mail list logo
