Breaking changes to network config settings


Paul Sokolovsky
 

Hello,

For the 1.13 release, networking configuration library ("net_conf") was
split from net_app library, because it always was independent from the
rest of net_app, and is useful even for apps which don't use net_app
(e.g. for apps using native low-level API, or BSD Sockets API). To
finish this refactor cleanly, one last step was to move related
Kconfig options from CONFIG_NET_APP_* namespace into separate
CONFIG_NET_CONFIG_* namespace.

All in-tree samples and tests were updated, but out of tree
networking applications will need to be updated separately by their
maintainers. Thanks to recent Kconfig improvements and behavior
tightening, there will be a clear-cut error message hinting about a
need to upgrade (instead of warning and incorrectly functioning
application like it could happen before).

For a reference on which Kconfig options need updates please see
commit
https://github.com/zephyrproject-rtos/zephyr/commit/028aae1ec9d5234a65ed4d4e99471fee3832ea7b

Alternatively, a shorter example of updating MicroPython Zephyr port:
https://github.com/pfalcon/micropython/commit/f27f79da52eae4e4ca2a89c70c711ef24249b3a5


--
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

Join devel@lists.zephyrproject.org to automatically receive all group messages.