This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Modifying SDK. Is that good practice?

Hello,

Is it a good practice to modify SDK files?

I mean, do you use SDK as integral part of your project and feel free to modify it, or do you try to avoid it and just use API's as it is?

This question is a little bit related to this: devzone.nordicsemi.com/.../

Parents
  • Totally agree with @emmanuel, usual practice is that you get the SDK source files, copy them to your project and modify there. During compilation you should have always project-specific PATH before SDK so modified files will get into the compilation/linking process (this is the way with compilation chains like GCC, can differ if you use different tools). And when you migrate to new SDK you check changes on these incriminated files and either port changes from new SDK into your project-specific files (if there is reason to keep your custom code) or abandon them and start using these from new SDK version (e.g. if it fixes the problem you were fixing manually before).

    Cheers Jan

Reply
  • Totally agree with @emmanuel, usual practice is that you get the SDK source files, copy them to your project and modify there. During compilation you should have always project-specific PATH before SDK so modified files will get into the compilation/linking process (this is the way with compilation chains like GCC, can differ if you use different tools). And when you migrate to new SDK you check changes on these incriminated files and either port changes from new SDK into your project-specific files (if there is reason to keep your custom code) or abandon them and start using these from new SDK version (e.g. if it fixes the problem you were fixing manually before).

    Cheers Jan

Children
No Data
Related