search

suriab / gyp

Automatically exported from code.google.com/p/gyp
0 stars 0 forks source link

includes should not be pulled in if the related target is not used #47

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently if any target in a gyp file is used, the entire gyp file is 
processed, including targets that 
are not used. This means that included gypi's get included, even if they are 
not relevant. Ideally, this 
would not happen, as this prevents gating in and out sections of a project.

Original issue reported on code.google.com by bradnel...@google.com on 13 Jul 2009 at 11:24

GoogleCodeExporter commented 9 years ago 
To clarify:  if you include a target in another .gyp file, all of that .gyp 
file's downstream 
includes *and* dependencies get pulled in and evaluated.  Right now, if it's a 
problem 
you just split the .gyp file.

Original comment by sgk@chromium.org on 6 Aug 2009 at 7:28