create a place where all generated files live that isn't dist/include

NEW
Unassigned

Status

Firefox Build System
General
--
enhancement
7 years ago
4 months ago

People

(Reporter: briansmith, Unassigned)

Tracking

Trunk

Firefox Tracking Flags

(Not tracked)

Details

Now, I tell my editor to look for files in src/ and in dist/include so that it can do code nagivation. However, for files that are copied from src/ to dist/include, this is really annoying, because the copies always get in the way (i.e. I will edit the copy instead of the file in src/). If we moved all the generated files to dist/include/generated, then this kind of code navigation would work out really well and save developers a lot of time.
The only thing I expect to be tricky here is 'make install'.
Yeah, I guess that is the point of dist/include. Another solution to the same problem would be to generate the header files into a single _xpidlgen directory instead of <x>/public/_xpidlgen, <y>/public/_xpidlgen. Or maybe this should be WONTFIXed.
Summary: move generated headers from dist/include to dist/include/generated → create a place where all generated files live that isn't dist/include

Updated

4 months ago
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.