Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
Help with programatically adding kit, debugger and device data
ErikL last edited by
I have a situation were a large number of Qt Creator users need to add kit, device, and debugger configurations. My thinking is to provide a plugin that does it (because fifty+ people cannot possibly all enter the data correctly in the GUI). I can see how a plugin can update the data that ends up in the .ini files, but cannot see what to do to get it into the .xml files that hold the kit, device, and debugger configurations. Any pointers about how to do this?
I thought about hacking the .XMLs, but there are certain fields (e.g, the internal IDs) that look like I could mess up and therefore corrupt the entry. Any pointers to how the value for this field is generated?
Any assistance is appreciated.
Best Regards, Erik
Each Creator has a GUID which is the id you see.
We have successfully appended data to the file, with
however, ended up using virtual machines as its much faster to
upgrade say the toolchain and device drivers in master WM and the other can
simply just grab the WM and be productive without any fiddling.
There is also
but it can say if it will work for your complete use case.
It certainly would be possible to make a Creator plugin that could import a settings file but
im not sure what API you should use for that.
I would go peeking around here
@mrjj is right with his points, I just like to add that MaintenanceTool is able to do exactly that, so a plugin could do it too.
But probably a script would already be enough.
ErikL last edited by ErikL
I recently learned about "sdktool"; it appears to be able to add kits and debuggers (and apparently devices, though it is not completely clear that feature is ready for use yet) from the command line. If it works as advertised, this is exactly what I was looking for.
Here are some links:
iieklund last edited by
Yes, the sdktool is the "API" to add kits etc. to creator. The Qt installers use the sdktool.