Exporters - uvision5 addition #1676
Conversation
|
I'm a little confused, so please forgive my ignorance. Since uvision5 supports uvision4 project files if you install the legacy support (http://www2.keil.com/mdk5/legacy), does it make sense to only export as uvision4? Otherwise, if we need to export to uvision5, then I think merging the files for uvision4 and uvision5 would be a good call. |
|
UV4 hasn't been developed for over a year and newer devices aren't supported in legacy packs. This means if we export for UV4 you can open a project that will not have device support. I think UV5 and the new file extension is the way to move forward. |
Yes, we can deprecate uvision4 later if ever. uvision5 currently has limited support in progen definitions (we will need to add more targets). I am pushing this forward as there was request for newer targets, which are available only for uvision5. I'll rebase this tomorrow, plus some testing with some more devices. |
|
I suggest full out moving to UV5 and dropping support for UV4 as that will solve some of the rather ugly hacks we have in place for UV4 to support Nordic BLE devices. Are there any devices that only exist in UV4 and not UV5? |
uvision5 uses software packs for devices, plus different extension. We should use uvision as uvision4. This is based on progen, same as uvision4.
|
All rebased , happy to merge? |
|
Good for now, we can always merge uvision4 and uvision5 into one file later |
uvision5 uses software packs for devices, plus different extension. We
should use uvision as uvision4. This is based on progen, same as uvision4.
At the moment it does not differ, I can merge uvision4 and 5 together into one file and reuse most of the code. suggestions?
@sg- @bridadan