Uh oh!
There was an error while loading. Please reload this page.
Add tool definition for cmake - #504
Conversation
dennisdoomen
commented
Jul 18, 2026
Should there not be a |
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
commented
Jul 18, 2026
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. |
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
You can generate the wrappers locally if you searching/fixing a wrapper bug. Edit: |
ChrisonSimtian
commented
Jul 19, 2026
look there is a series of things on this topic, but tldr is: commit the |
ChrisonSimtian
commented
Jul 19, 2026
oh and since this one is a tad grave digging (4 year old PR), lets make sure that the cmake stuff is still up2date please, yes? :-) |
IT-VBFK
commented
Jul 19, 2026
I already asked AI to add missing parameters and check the rest. Since I don't use cmake either (I'm a 100% .NET guy) we have to rely on actual c/c++ devs I suppose 🫣 |
From here: nuke-build/nuke#1006
Thanks @MoodieG