![]() Luckily, the SDK has been stabilized the past year very much, so chances are high that things will just compile by now. Well, only if there are no API changes in the SDK. Then make sure to update the code: Update CodeĬonfirm to update the code and you shall be all set :-). This triggers a dialog informing me that new data gets loaded which is fine: Next I re-add SDK Part support: Add SDK Part Support Config Tools So I do it manually: I delete the old files and now I’m able to build the project: Build works fine Part Support However, the ‘Refresh SDK’ action somehow has not changed them too. This might fail because most likely the SDK could have changed files as below: Added Files with New NamesĪs in the case above, the names have changed for a reason. The next thing would be an attempt to compile the project. Now it should show that the SDK version has been upgraded: Updated Version This will show a dialog about the updated/added files. As a first step I remove the existing part support (if any) to have it clean: Remove SDK Part Support from Project To make projects work without an SDK installed, I usually have ‘Part support’ added: that way for example the debugger has all the needed information. So here is my case: I do have an existing project on SDK v2.8.2 and I do want to upgrade it to the v2.9.0 version: Part Support The other reason for upgrading is if (for whatever reason) the zip file for that old SDK is not available, but there is a newer version installed. And in a class room environment I can be on the same latest and greatest SDK as my students are using. But if I want to take advantage from latest bug fixes or features it makes sense. In general it is not necessary to upgrade a project. While things work pretty well for me migrating SDKs recently, it might not be the case for a particular (old) SDK. I’m using git (which I recommend to everyone) for this. ![]() In this post I’ll show how an existing project can be upgraded to use a new SDK.įirst: make a backup of your project. ![]() But from time to time it makes sense to upgrade a project to a newer version. This is great because I do want to have control over what SDK is used. My lab projects get used over multiple semesters, and the MCUXpresso projects by default use the SDK version used at that time. As time flies by, my projects are evolving.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |