I was looking into adopting swift packages plug ins for generating Djinni source code to bridge Swift to C++. Djinni generates C++ and Objective-C++ code. It appears the plug in build tools do not support generated header files because the search path is not passed to the internal and public code that requires it to compile. It also attempts to compile the header files which it warns that it doesn't know how to handle.
The plug in build command needs to provide the public and internal search paths that are needed to compile the non-generated source that depends on what the build tool generated. For my purpose, this would include a non-generated folder that the Djinni package provides. The internal header search paths would be passed to all internal generated and non-generated source. The public header search paths would be passed to all internal generated and non-generated source and any package that depends on this package.
Add a new c-style-supported buildCommand and prebuildCommand APIs that have parameters for arrays of internal and public header search path folders paths.