external: split Kconfig for each module
authorsunghan <sh924.chang@samsung.com>
Fri, 22 Sep 2017 12:21:30 +0000 (21:21 +0900)
committersunghan <sh924.chang@samsung.com>
Fri, 22 Sep 2017 12:21:30 +0000 (21:21 +0900)
commit6f5c82fabdf4956c6f26fa5175abafcff851bb52
treea7bf0553019e9f3abcc196d065895c3171433d03
parent09cb6a6a9cc68598dcbd9abe12fcdb44e478bb16
external: split Kconfig for each module

Each module had better have an independent Kconfig. Putting all of configs
in one Kconfig makes bad readability and maintenance.
The Kconfig on external gets a functionality calling each Kconfig.
external/Kconfig
external/aws/Kconfig [new file with mode: 0644]
external/iotivity/Kconfig [new file with mode: 0644]
external/libtuv/Kconfig [new file with mode: 0644]
external/wakaama/Kconfig [new file with mode: 0644]