FILE_SET: Add RESOURCE file set type
I have a situation where I need to allow a target to describe a file that is not a source file (e.g. not cpp, or c, or anything of the like) or header file, which must be installed along side the library that the target builds.
This target is very very early in the build process, and managed by a team that has nothing to do with the team that manages the installation process.
As such, the installation team's code has no knowledge of this special file. They only know that the target in question is a very low level recursive dependency of one of the applications being installed.
I'm currently attempting to abuse the FILE_SET feature so that there can be a "well known" file set name that any library target can add files to, in order to be installed along-side the library.
It would be nice if a new type of file set, "ARBITRARY" or "BINARY" or "PREBUILT" or whatever like that, could be supported so that files like this are not confused with the header verification functionality that the FILE_SET feature is related to.