Open GoogleCodeExporter opened 9 years ago
One possible backward compatible solution would be to expose
"_sources_included" to
variable expansions.
Original comment by y...@chromium.org
on 30 Dec 2009 at 12:03
Original comment by bradnelson@google.com
on 25 Jan 2010 at 1:43
Any update on this? It's holding up a webkit patch that will make builds much
faster.
Original comment by jor...@chromium.org
on 17 Feb 2010 at 5:15
/ and ! intentionally happen really late in the game. It's not easy to get
them to happen
earlier (before variable expansion time).
Original comment by mark@chromium.org
on 17 Feb 2010 at 6:38
This issue blocks https://code.google.com/p/chromium/issues/detail?id=371513,
fixing which requires us to specify an explicit list of inputs passed to a
python script.
Original comment by apav...@chromium.org
on 12 May 2014 at 11:10
> / and ! intentionally happen really late in the game
Any insight into why this is intentional? In particular, why ordinary
compilation targets can make use of the filtered "sources" while actions (in
our case, it's a JavaScript compilation step executed as a python script)
cannot?
Original comment by apav...@chromium.org
on 12 May 2014 at 1:33
Original issue reported on code.google.com by
y...@chromium.org
on 30 Dec 2009 at 11:52