Open billev opened 1 month ago
Working on this issue.
Thanks for reporting the issue. I assume that you were able to manually remove the "disabled" component so you are not blocked. Just a question, does the uVision project have multiple targets or just one? If it just has one, could you add a second target without any other modifications and let me know whether the disabling of components is now working in the converted solution?
Fixed. Node "not-for-context" was added to point out excluded components in .cproject file.
Change will appear in next release uv2csolution 1.5.0.
Type: Bug Report
Bug Description When importing an existing uVision project, components that are marked for non-inclusion in the build (that is, don't have "Include in Target Build" checked) are nonetheless included in the build.
I imported an existing uVision project. Over time we've used different NOR flash chips, support for which had been added to the project, then turned off as no longer needed. I imported that to Arm CMSIS Solution, and those components were imported (ok), and included in the build (not ok), leading to duplicate symbol errors at link time.
To Reproduce Steps to reproduce the behavior:
Expected behavior Components marked as "DO NOT Include in target build" should not be included in the component list in the .cproject.yml file.