Add tool definition for cmake

[IT-VBFK]

From here: nuke-build/nuke#1006

Thanks @MoodieG

[dennisdoomen]

Should there not be a .generated.cs file as well?

[IT-VBFK]

Hmmm... the contribution guidelines stating to explicity not to commit generated tool files (since they are done once before a release).

If this should be different here vs. NUKE this may should be mentioned.

[fredericvaillancourt]

Adding myself to the discussion to get the tool generated answer. Generated my files but it does change the generated from (url) ... several places in every tools ... In fact the current url is from a form and not even the official. Personally I don't like generated files in source control except when they are quite difficult to generate. Waiting to get a definitive answer before I make my PR.

[IT-VBFK]

I vote for removing them all, because fixing errors in tools wrappers has to go into the json anyway and would be overwritten when not done).

I imagine following workflow

• add the GenerateToolSettings as additional release pipeline executed target
• these files (intermediately generated) compiles into the production assetes (dll/nuget package).

You can generate the wrappers locally if you searching/fixing a wrapper bug.

Edit:
Ok.. I found a few tool wrappers who wraps a nuget package. These wrappers use partial classes and reference a generated value in this additional partial class.