Neil Mitchell

CC @aherrmann (with no obligation to fix). I'll raise a diff to document the restriction so at least it is clear.

Anything under `docs/legacy` isn't real docs. They seem to be confusing more than they are helpful. I'm going to hide them now, sorry for the confusion. If your project is...

> I don't believe those cpp files will be uploaded to RE when compiling the cxx_library, because buck doesn't know about them I think Buck2 will know about them. The...

@AtomicOperation I think `public_include_directories` is a bit of a hack. I think if you use `header_dirs` instead it will let you specify a `$location`. Maybe that's what @zjturner is after...

Custom rule returning CPreprocessorInfo _or_ `header_dirs` should both work for that.

We haven't got the Apple toolchain working for non-FB developers - it points at internal things we haven't yet made available. It's on our todo list, but with no guarantee...

We plan to support everything on that list, and basically everything in the prelude that has rules for should eventually work both internally and open source.

The expectation is that the resources.json lives relative to the binary itself. You can't change the working directory of the binary when it runs as that is probably important to...

You can do most things with a genrule - e.g. make it ```python genrule( name = "exe", cmd = "cp $(location //target:exe) $OUT/exe && cp $(location //target:resources) $OUT/resources)", ) ```...

If you had a binary `id.sh` which just ran whatever it got given, then I think: ``` sh_test( name = "foo-test", test = "id.sh", args = ["$(exe :foo)"], ) ```...