Every now and then I hit a case when silently including ~/.gyp/include.gypi
leads to confusion when comparing different build configurations (i.e. between
developers or between builder machines).
Usually we don't need include.gypi (right?) so printing out
"WARNING: Including ~/.gyp/include.gypi"
should be fine.
Original issue reported on code.google.com by timurrrr@chromium.org on 17 May 2011 at 11:56
Original issue reported on code.google.com by
timurrrr@chromium.org
on 17 May 2011 at 11:56