1config 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
19	  Mender Connect is loosely coupled with the Mender Client. The
20	  main information passed between mender-client and
21	  mender-connect is the device authorization status. Since only
22	  accepted devices can interact with the Mender Server, the
23	  Mender Client passes over DBus the authorization token which
24	  Mender Connect uses to establish a Websocket connection to the
25	  server.
26
27	  https://github.com/mendersoftware/mender-connect
28
29comment "mender-connect needs a toolchain w/ threads, wchar"
30	depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
31	depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
32	depends on BR2_USE_MMU
33	depends on !BR2_TOOLCHAIN_HAS_THREADS || !BR2_USE_WCHAR
34