ヘルプ
英语（美国） | English (US) 日本語 | Japanese 中文 | Chinese (Simplified)

Migrating an application between different SDK versions using MCUXpresso

キャンセル
提案をオンにする
自動提案では、入力時に可能な一致が提案されるので検索結果を素早く絞り込むことができます。
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 
解決済み
ソリューションへジャンプ

Migrating an application between different SDK versions using MCUXpresso

ソリューションへジャンプ
‎09-14-2021 06:54 AM
2,560件の閲覧回数
Ricardo3
NXP Employee
NXP Employee

We have a situation where we have an application project built on top of an existing SDK. We then get a new version of the SDK where some files are renamed/moved. That means that the application .project and .cproject need to be updated for the new SDK version. However, we have not found a way to do this except by hand comparing .cproject files and making the changes by hand. Also for files that are not changed, in new SDK versions, the .cproject files are changed with some magic numbers.

What is the recommended way to migrate application project files to a new SDK version? How can we keep our application and take in the new SDK files when a new release is received?

返信
1 解決策

ソリューションへジャンプ
‎09-14-2021 07:45 AM
2,558件の閲覧回数
ErichStyger
Specialist I

Not sure if there is a recommended way, but I would say in general it would not be recommended to switch SDKs, because as you noticed there might be breaking changes.

What I'm using is the process I have described in https://mcuoneclipse.com/2021/04/27/upgrade-to-a-new-nxp-mcuxpresso-sdk/

Additionally I feel it is mandatory to have your project in a version control system (I'm using git/GitHub/GitLab, see https://mcuoneclipse.com/2018/09/30/tutorial-git-with-eclipse/ which allows me to track changes and always go back if necessary.

One thing to look out for is that some folders might get 'excluded from build', so you have to re-enable them, see https://mcuoneclipse.com/2014/07/22/exclude-source-files-from-build-in-eclipse/

I hope this helps,

Erich

元の投稿で解決策を見る

返信
2 返答（返信）

ソリューションへジャンプ
‎09-14-2021 08:04 AM
2,553件の閲覧回数
Ricardo3
NXP Employee
NXP Employee

Hi Erich

Thank you for your answer. Actually, we have no alternative but to switch SDKs. We are using SDKs that are fully under development and every few months we get an update that we need to migrate our applications to.

I think the link you sent could be useful, so i am checking that, but i am also concluding that it's unavoidable having some manual work required, which is not ideal if we have multiple applications with multiple configurations.

I'll keep this topic open for if someone else has a better suggestion.

0 件の賞賛
返信

ソリューションへジャンプ
‎09-14-2021 07:45 AM
2,559件の閲覧回数
ErichStyger
Specialist I

Not sure if there is a recommended way, but I would say in general it would not be recommended to switch SDKs, because as you noticed there might be breaking changes.

What I'm using is the process I have described in https://mcuoneclipse.com/2021/04/27/upgrade-to-a-new-nxp-mcuxpresso-sdk/

Additionally I feel it is mandatory to have your project in a version control system (I'm using git/GitHub/GitLab, see https://mcuoneclipse.com/2018/09/30/tutorial-git-with-eclipse/ which allows me to track changes and always go back if necessary.

One thing to look out for is that some folders might get 'excluded from build', so you have to re-enable them, see https://mcuoneclipse.com/2014/07/22/exclude-source-files-from-build-in-eclipse/

I hope this helps,

Erich

返信