Hello!As an author of CMake <> uVision Synchronizer project, I am trying to find a list of all possible (or at least all mandatory) configuration options in uVision5 Project File (.uvprojx) and uVision5 project options (.uvoptx) XML files.Now the project is developed mostly by trial-and-error by testing on Nordic nRF5 SDK project files, which is very time-consuming and error prone. And when "everything works", the script gets tested on a project file generated by STM32Cube and there are new errors on account of new, missing or different configuration options.I have checked the uVision Application Notes, Appendix B. File Types, Appendix C. Device Database Parameters and other sources found on the internet, however I could not find even list of options (I gave up the hope of also having the parameter descriptions).I would be really grateful for any information regarding this topic, as developing the CMake -> uVision part of the project is nearly impossible without actually knowing which config options are important.Thank you,Bojan
all kinds of project settings are stored in *.uvprojx, *.uvoptx and *.uvguix files. They are XML file format based. When you check or read the XML element names, you could understand what options they are meant for.
However, please note these files are propertied files, which means we can change the way and position of an option to be stored in such files, as long as it is still compatible with MDK uVision. Thus, unfortunately we cannot list the details of options how and where they are stored in these files.
In other words, these project files are not meant or designed to be converted to other third party IDE project files
Let's say that I need to frequently Activate and Deactivate `Browse Information` - Activate for Normal Developing and Deactivate for Batch Processing; then, I'm encouraged to either do this manually, or regex the uvprojx, instead of creating a xml template file?
Create separate 'Targets' - one with & one without Browse Info ... ?
But why would you want to keep changing? Why not just keep it enabled?
In other words, vendor lock-in?
This looks like a good start. https://www.keil.com/appnotes/files/apnt_279.pdf