Many different jobs are implemented using different executables in the cg3 suite[^1].
This is nice, that the LLVM toolings' (subpar) argument parser does not virally infest things it has no reason to.
And allows us to actually run in a way we want.
However, we will have a lot of different executables if we keep this model up, and continue to add more and more things to the project.
Therefore, a central driver executable is needed, which knows which executable to call with the correct parameters, according to the required parameters.
This would even allow us to abstract away the LLVM argument parser, which is majorly painful to use in a libTooling tool, which cg3-check is.
Many different jobs are implemented using different executables in the cg3 suite[^1].
This is nice, that the LLVM toolings' (subpar) argument parser does not virally infest things it has no reason to. And allows us to actually run in a way we want.
However, we will have a lot of different executables if we keep this model up, and continue to add more and more things to the project. Therefore, a central driver executable is needed, which knows which executable to call with the correct parameters, according to the required parameters.
This would even allow us to abstract away the LLVM argument parser, which is majorly painful to use in a libTooling tool, which cg3-check is.
[^1]: Yes, I'm arrogant enough to call it a suite