[cfe-commits] [patch] fix -include relative path .d file generation

[Nick Lewycky]

Ping!

I still think this patch is Kinda Ugly, but we've been running with it for
about a month now. Please review!

Link to original post with attachment:
http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20110207/038571.html

Nick

On 15 February 2011 18:47, Nick Lewycky <nlewycky at google.com> wrote:

> Hi,
>
> There's a small difference between gcc and clang in emitted .d files when
> -include was passed a relative path. Sadly, this actually breaks our build
> system. GCC preserves what the user wrote in the argument while clang
> replaces it with an absolute path. That breaks for us because we try to
> relocate those files afterwards.
>
> This moderately gnarly patch extends an existing hack to insert the file
> specified in the -include path first, and any subsequent #include lookups
> will find the same file with the first path is was looked up with.
>
> Please review!
>
> Nick
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20110222/f188159e/attachment.html>