Config.in 1.4 KB

123456789101112131415161718192021222324252627282930313233
  1. config BR2_PACKAGE_MENDER_CONNECT
  2. bool "mender-connect"
  3. depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
  4. depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
  5. depends on BR2_TOOLCHAIN_HAS_THREADS # libglib2, mender
  6. depends on BR2_USE_WCHAR # libglib2 -> gettext
  7. depends on BR2_USE_MMU # dbus -> fork()
  8. select BR2_PACKAGE_DBUS # runtime
  9. select BR2_PACKAGE_LIBGLIB2
  10. select BR2_PACKAGE_MENDER # runtime
  11. select BR2_PACKAGE_OPENSSL
  12. help
  13. mender-connect is a daemon responsible for handling
  14. bidirectional (websocket) communication with the Mender
  15. server. The daemon is responsible for implementing a range of
  16. troubleshooting features to the device as well as several
  17. enhancement to the mender-client.
  18. Mender Connect is loosely coupled with the Mender Client. The
  19. main information passed between mender-client and
  20. mender-connect is the device authorization status. Since only
  21. accepted devices can interact with the Mender Server, the
  22. Mender Client passes over DBus the authorization token which
  23. Mender Connect uses to establish a Websocket connection to the
  24. server.
  25. https://github.com/mendersoftware/mender-connect
  26. comment "mender-connect needs a toolchain w/ threads, wchar"
  27. depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
  28. depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
  29. depends on BR2_USE_MMU
  30. depends on !BR2_TOOLCHAIN_HAS_THREADS || !BR2_USE_WCHAR