[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: parse-datetime.c generated in the source (instead of build) director

From: Bruno Haible
Subject: Re: parse-datetime.c generated in the source (instead of build) directory
Date: Mon, 19 Mar 2018 20:59:49 +0100
User-agent: KMail/5.1.3 (Linux/4.4.0-116-generic; KDE/5.18.0; x86_64; ; )

> Other source files are captured just fine.  The only problem is that it
> expects parse-datetime.{c,y} to be in build directories, instead of the
> source directory.  It could be confused by the #line directives that bison
> produces.

Indeed, that could be. OTOH, tools like bison and gperf should *not* put
relative directories into #line directives, because such relative directories
would often depend on whether it's a VPATH build or not, and when the tool
was run on a Windows system, the relative directory might contain backslashes
as directory separator characters.

So, I think that tools that interpret debugging information should have a
way to specify a set of source directories. Like gdb does.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]