Replacing printf() with fprintf() in this code section aims to
prevent unpredictable behavior in multi-threaded environments that
could be caused by printf()'s non-atomic nature. The change is
intended to enhance output consistency and prevent potential race conditions.
Additionally, it is important to note that many other plain calls to printf()
in the Neutrino code could also cause issues and require further investigation.
Whether this change will have a positive impact remains to be seen.
Added more documented output for users and removed some unused
lines (such as assignments after AC_MSG_ERROR, which do not make sense).
Additionally, more checks have been added with result output.
DEBUG_CFLAGS can now be used as an environment variable.
This change was made because for debugging purposes, users should be
able to adjust the options, rather than relying solely on static options
such as -g3 -ggdb. This is especially important since -O2 may often
not be sufficient.
Do we really need the CDK mode? Would it be a better idea to
handle this via the usual configuration or build system, using
environment variable assignments, or catching specific cases
in a makefile? Additionally, I have the impression that hardly
anyone is using the CDK mode.
Note: This line: 'TARGET_PREFIX "/share/zoneinfo/" + zone' will be
found in other source files too. It could make
sense to unify it globally to avoid duplicating code.
'getter' methods do convey a return value,
but getLiveStreamInfo() returns nothing, therefore we should use
a more appropriate name, such as 'initialize'
or 'modify', improving code clarity and adherence
to best practices.
Signed-off-by: Thilo Graf <dbt@novatux.de>
Conflicts:
data/locale/deutsch.locale
data/locale/english.locale
src/system/locals.h
src/system/locals_intern.h
Detected: LOCALE_INETRADIO_AUTOSTART,
LOCALE_INETRADIO_NAME,
These entries were messed because of different use of dots and
underlines in locales.
Was broken here, and it's easier for users of package manager to
handle since last changes of package manager, and it's easier to
maintain class CFlashUpdate without impact of package manager.
