I am using the Google Filament rendering library in my C++ game physics engine prototype. This library comes with a compiler to convert its custom format material definitions into binary blobs which can be themselves compiled into the executable via a generated header file and .S file.
I have a custom build rule which builds these files into their correct outputs no problem, but I cannot find a way to add their outputs to the Compile Sources phase in a way where the dependencies get picked up correctly (first time I build I get missing file errors) and Archiving is completely broken as it cleans before building. The interface does not seem to understand its own ($DERIVED_FILE_DIR) path when trying to Compile Sources and so does not pick up on the dependencies correctly.
How should this work?