<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - [recent build error] glsl_parser.h: No such file or directory" href="https://bugs.freedesktop.org/show_bug.cgi?id=56685#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - [recent build error] glsl_parser.h: No such file or directory" href="https://bugs.freedesktop.org/show_bug.cgi?id=56685">bug 56685</a> from <a class="email" href="mailto:thierry.reding@avionic-design.de" title="Thierry Reding <thierry.reding@avionic-design.de>"> Thierry Reding</a> <pre>(In reply to <a href="show_bug.cgi?id=56685#c12">comment #12</a>) > How could glsl_parser.h exist in both src and build directories? There could be any number of reasons. The most likely would be if somebody's built in-tree, so glsl_parser.h gets generated in the source tree, and then decides to build out-of-tree. Granted, a proper build system would detect and prevent that, but I'm not sure we're there yet. There's also always the possibility of somebody just copying it there. But my point was that it usually is a sensible decision to prefer the contents of the build tree over those of the source tree. I've seen lots of packages that were broken in some subtle way and would specifically generate files in the build tree, but then go and reuse the one that shipped in the source tree. Such bugs can be very hard to find and they usually aren't obvious from the start, so if there's an easy way to avoid them I think we should do so.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>