When compiling for other platforms than Broadcom, the broadcom feed with
its packages does not exist, so ignore the error if the file does not
exist.
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
Move bcm-toolchain.mk to further to the top so that the appending to
TARGET_CFLAGS with -Wall -Werror in this file is done properly and not
overridden.
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
Do not set CFLAGS and others explicitly for BCM, the ones set by
bcm-toolchain.mk since feeds/broadcom commit 3191be5482a8 (bcmkernel:
toolchain: Set more flags and tools, 2024-04-17) are sufficient.
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
CheckDependencies failed because DT_RUNPATH had not been set. Since
commit 084691a29a (voicemngr: Do not manually specify BCM lib paths,
2024-03-25) we do set a proper RUNPATH, so we can re-enable dependency
checking.
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
This is no longer necessary since feeds/broadcom commit 3191be5482a8
(bcmkernel: toolchain: Set more flags and tools, 2024-04-17).
Signed-off-by: Andreas Gnau <andreas.gnau@iopsys.eu>
* sshmngr uci is deprecated and so are the library functions
related to managing that uci, sshmngr will directly interact
with the backend uci now
* a compile time flag is introduced which tells sshmngr code
whether dropbear backend is being used or not
if backend uci is changed then restarting sshmngr can lead to
those changes being lost, try to preserve some of the changes
the following behaviour has been tested:
* if an extra option is set in backend UCI which is not set in
sshmngr UCI for the same section, it will stay as it is
* manually added section in backend is not over-written
* sshmngr managed sections are properly added/modified/deleted
* option BbfSection is introduced which can be set to 0 to prevent
sshmngr from modifying a backend section
the above works except for first boot (then sshmngr will override
backend UCI)
