From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/qt5/qt5base: add -syslog option
Date: Wed, 4 Nov 2020 11:33:31 +0100 [thread overview]
Message-ID: <20201104113331.03437e4a@gmx.net> (raw)
In-Reply-To: <20201103221817.213528-1-jzignego@hedcontrols.com>
Hello Jeff,
On Tue, 3 Nov 2020 16:18:17 -0600, jzignego--- via buildroot <buildroot@busybox.net> wrote:
> From: Jeff Zignego <jzignego@hedcontrols.com>
>
> When using sysvinit (or the busybox implementation) qt5 can output log
> messages to the traditional syslog with the -syslog compile time
> option. This is very similar to the -journald compile time option
> already being leveraged in qt5base.mk
>
> Signed-off-by: Jeff Zignego <jzignego@hedcontrols.com>
> ---
> package/qt5/qt5base/qt5base.mk | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/package/qt5/qt5base/qt5base.mk b/package/qt5/qt5base/qt5base.mk
> index ed308c1fa2..d9b8ff279b 100644
> --- a/package/qt5/qt5base/qt5base.mk
> +++ b/package/qt5/qt5base/qt5base.mk
> @@ -254,6 +254,20 @@ else
> QT5BASE_CONFIGURE_OPTS += -no-journald
> endif
>
> +ifeq ($(BR2_PACKAGE_SYSVINIT),y)
> +QT5BASE_CONIGURE_OPTS += -syslog
> +QT5BASE_DEPENDENCIES += sysvinit
> +else
> +QT5BASE_CONFIGURE_OPTS += -no-syslog
> +endif
> +
> +ifeq ($(BR2_PACKAGE_INIT_BUSYBOX),y)
> +QT5BASE_CONIGURE_OPTS += -syslog
> +QT5BASE_DEPENDENCIES += busybox
> +else
> +QT5BASE_CONFIGURE_OPTS += -no-syslog
> +endif
> +
This would result in busybox overwriting the sysvinit case, e.g. with
BR2_PACKAGE_SYSVINIT set and BR2_PACKAGE_INIT_BUSYBOX unset:
QT5BASE_CONFIGURE_OPTS = ... -syslog -no-syslog ...
Not an init/syslog expert, but I believe the syslog feature is independent
of the init system used (as long as a some daemon is listening on the /dev/log
socket, something which even works with systemd) and the used syslog.h
header file is provided by the C library already (no need for another
compile time dependency)...
For the Qt syslog feature I would suggest an extra config option
(as some other packages do already, see e.g. BR2_PACKAGE_COLLECTD_SYSLOG,
BR2_PACKAGE_WPA_SUPPLICANT_DEBUG_SYSLOG), because enabling this
changes the default Qt logging from stderr to syslog (see
qt5base-5.15.1/src/corelib/global/qlogging.cpp), something
not every user is expecting (yes I know this is not symmetrical
for the systemd buildroot handling)...
Regards,
Peter
> ifeq ($(BR2_PACKAGE_IMX_GPU_VIV),y)
> # use vivante backend
> QT5BASE_EGLFS_DEVICE = EGLFS_DEVICE_INTEGRATION = eglfs_viv
next prev parent reply other threads:[~2020-11-04 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 22:18 [Buildroot] [PATCH 1/1] package/qt5/qt5base: add -syslog option jzignego at hedcontrols.com
2020-11-04 10:33 ` Peter Seiderer [this message]
2020-11-04 18:56 ` Jeff Zignego
2020-11-04 18:12 ` [Buildroot] [PATCH v2 " jzignego at hedcontrols.com
2020-11-07 13:46 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201104113331.03437e4a@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox