From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/modem-manager: enable qcom-soc if libqrtr-glib enabled
Date: Mon, 5 Apr 2021 12:17:38 +0200 [thread overview]
Message-ID: <YGrjwp8R7/J4vW9q@pevik> (raw)
In-Reply-To: <20210405110250.1e48e10f@windsurf.home>
> On Sun, 4 Apr 2021 20:41:26 +0200
> Petr Vorel <petr.vorel@gmail.com> wrote:
> > This plugin makes sense only for Qualcomm MSM phone.
> > Although there is currently no such device defconfig in Buildroot yet,
> > it makes sense to prepare modem-manager for it.
> > Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> > ---
> > package/modem-manager/modem-manager.mk | 6 ++++++
> > 1 file changed, 6 insertions(+)
> > diff --git a/package/modem-manager/modem-manager.mk b/package/modem-manager/modem-manager.mk
> > index 2cc45d266b..d62d13cf45 100644
> > --- a/package/modem-manager/modem-manager.mk
> > +++ b/package/modem-manager/modem-manager.mk
> > @@ -34,6 +34,12 @@ else
> > MODEM_MANAGER_CONF_OPTS += --without-mbim
> > endif
> > +ifeq ($(BR2_PACKAGE_LIBQRTR_GLIB),y)
> > +MODEM_MANAGER_CONF_OPTS += --enable-plugin-qcom-soc
> Isn't that missing a MODEM_MANAGER_DEPENDENCIES += libqrtr-glib line ?
> Or is it really a runtime dependency ?
error: Couldn't find libqmi-glib >= 1.29.3
when building locally.
=> you're right it probably requires MODEM_MANAGER_DEPENDENCIES += libqrtr-glib
I'll test it and probably sent v2.
Thanks for catching error!
Kind regards,
Petr
> Thomas
next prev parent reply other threads:[~2021-04-05 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 18:41 [Buildroot] [PATCH 1/1] package/modem-manager: enable qcom-soc if libqrtr-glib enabled Petr Vorel
2021-04-05 9:02 ` Thomas Petazzoni
2021-04-05 10:17 ` Petr Vorel [this message]
2021-04-05 13:44 ` Petr Vorel
2021-04-05 14:36 ` Thomas Petazzoni
2021-04-05 14:45 ` Aleksander Morgado
2021-04-05 15:51 ` Petr Vorel
2021-04-06 7:29 ` Aleksander Morgado
2021-07-25 21:32 ` Thomas Petazzoni
2021-07-25 21:34 ` Petr Vorel
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=YGrjwp8R7/J4vW9q@pevik \
--to=petr.vorel@gmail.com \
--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