This is unlikely to be implemented (I won't go so far as to WontFix this, but brettw@ might).

There's no good way to implement this correctly such that we know when to regenerate the build files when the results of the glob changes.

We do (kinda) support this for specifying data file dependencies on a directory, so you can specify a directory that will get its contents included into an isolate for swarming, but that won't actually let you compile things.

I suppose I don't actually know what you mean by 'corpus' in your example; or how you would use it. If those are data files passed to tests, then maybe what we support is good enough?

You can also implement this using exec_script(). E.g.:

https://code.google.com/p/chromium/codesearch#chromium/src/build/config/android/rules.gni&q=exec_script%20find%20file:%5C.gn&sq=package:chromium&type=cs&l=2212

However, I hope to stop doing this in Android for the reason Dirk mentioned (GN doesn't notice when the glob changes, so doesn't automatically regenerate files). What I hope to change *to* is having generated checked in files that contain the result of find.py. That way when you add / remove a file, you'll need to re-generate the file list and GN will notice that.

I've changed my mind, and am wontfix'ing it :).