All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/alsa-utils: update dependency for topology support
Date: Sat, 5 Nov 2022 21:46:52 +0100	[thread overview]
Message-ID: <20221105214652.6dde4702@windsurf> (raw)
In-Reply-To: <20221105074444.13360-1-bernd.kuhls@t-online.de>

Hello Bernd,

On Sat,  5 Nov 2022 08:44:44 +0100
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:

>  config BR2_PACKAGE_ALSA_UTILS_ALSATPLG
>  	bool "alsatplg"
> -	depends on !BR2_STATIC_LIBS # dlfcn.h
> -
> -comment "alsatplg needs a toolchain w/ dynamic library"
> -	depends on BR2_STATIC_LIBS
> +	depends on BR2_PACKAGE_ALSA_LIB_TOPOLOGY

I'm wondering why you're doing it like this, and not in the normal way:

config BR2_PACKAGE_ALSA_UTILS_ALSATPLG
        bool "alsatplg"
        depends on !BR2_STATIC_LIBS # alsa-lib topology
	select BR2_PACKAGE_ALSA_LIB_TOPOLOGY

comment "alsatplg needs a toolchain w/ dynamic library"
        depends on BR2_STATIC_LIBS

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-11-05 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05  7:44 [Buildroot] [PATCH 1/1] package/alsa-utils: update dependency for topology support Bernd Kuhls
2022-11-05 20:46 ` Thomas Petazzoni via buildroot [this message]

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=20221105214652.6dde4702@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd.kuhls@t-online.de \
    --cc=thomas.petazzoni@bootlin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.