Modifying SDK. Is that good practice?

RE: Modifying SDK. Is that good practice?

Roger Clark — Wed, 08 Mar 2017 06:43:18 GMT

I totally agree with both @endnode and @Emmanuel

You should not change anything inside the SDK at all.

This includes even adding a custom header file for a custom board, hence see my post / question about making sure your project source code is completely isolated from the SDK.

In your case, I think you'd need to duplicate the files that you need to modify and change your makefile to use your copies instead of the SDK version

RE: Modifying SDK. Is that good practice?

endnode — Tue, 07 Mar 2017 18:24:22 GMT

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

RE: Modifying SDK. Is that good practice?

manymany — Tue, 07 Mar 2017 15:46:06 GMT

For me it is not a good idea because when you want to update the SDK 12.2 ->12.3 for instance you lose your modifications.