OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/net/lib/mqtt_packet/prj.conf

10 lines
166 B
Plaintext
Raw Normal View History

iot/mqtt: Add test app for the MQTT packet handling routines The following routines are evaluated in this test case: - mqtt_pack_connect - mqtt_pack_disconnect - mqtt_pack_publish - mqtt_pack_subscribe - mqtt_pack_suback - mqtt_pack_pingreq - mqtt_pack_pingresp - mqtt_pack_puback - mqtt_pack_pubcomp - mqtt_pack_pubrec - mqtt_pack_pubrel - mqtt_pack_unsuback - mqtt_unpack_connect - mqtt_unpack_disconnect - mqtt_unpack_pingreq - mqtt_unpack_pingresp - mqtt_unpack_puback - mqtt_unpack_pubcomp - mqtt_unpack_pubrec - mqtt_unpack_pubrel - mqtt_unpack_unsuback Future patches will extend this test case to cover the whole MQTT packet library. Origin: Original Jira: ZEP-870 Change-Id: I4fee403c24d1eb0428fb18b413763e28b6b726d1 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-11-08 14:24:53 +08:00
# required for htons
CONFIG_NETWORKING=y
# native IP stack support
random: Restructure RANDOM Kconfig Restructure the RANDOM Kconfig to match the structure used in other drivers with a single top level menu. Move the true random number generators to appear first in the menu, with pseudo generators at the bottom. Do not present pseudo generators if a true random generator is presented. This change implies that tests, samples and applications that require the random driver interface must now select CONFIG_RANDOM_GENERATOR. In order for tests and samples to build (and run) on platforms that have no random driver it remains necessary to select the CONFIG_TEST_RANDOM_GENERATOR. Note that CONFIG_TEST_RANDOM_GENERATOR retains its original purpose of enabling a random driver that delivers non random numbers for the purpose of testing only. Change-Id: I2e28e44b4adf800e64a885aefe36a52da8aa455a Signed-off-by: Marcus Shawcroft <marcus.shawcroft@arm.com>
2016-11-29 04:39:43 +08:00
CONFIG_RANDOM_GENERATOR=y
iot/mqtt: Add test app for the MQTT packet handling routines The following routines are evaluated in this test case: - mqtt_pack_connect - mqtt_pack_disconnect - mqtt_pack_publish - mqtt_pack_subscribe - mqtt_pack_suback - mqtt_pack_pingreq - mqtt_pack_pingresp - mqtt_pack_puback - mqtt_pack_pubcomp - mqtt_pack_pubrec - mqtt_pack_pubrel - mqtt_pack_unsuback - mqtt_unpack_connect - mqtt_unpack_disconnect - mqtt_unpack_pingreq - mqtt_unpack_pingresp - mqtt_unpack_puback - mqtt_unpack_pubcomp - mqtt_unpack_pubrec - mqtt_unpack_pubrel - mqtt_unpack_unsuback Future patches will extend this test case to cover the whole MQTT packet library. Origin: Original Jira: ZEP-870 Change-Id: I4fee403c24d1eb0428fb18b413763e28b6b726d1 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-11-08 14:24:53 +08:00
CONFIG_TEST_RANDOM_GENERATOR=y
# enable the MQTT lib
CONFIG_MQTT_LIB=y