Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Romain Naour <romain.naour@gmail.com>,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/supertuxkart: fix build with bluetooth enabled
Date: Sat, 22 Jul 2023 23:28:53 +0200	[thread overview]
Message-ID: <20230722232853.29d39f2c@windsurf> (raw)
In-Reply-To: <20230716135557.4180899-1-bernd@kuhls.net>

Hello Bernd,

On Sun, 16 Jul 2023 15:55:57 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:

> The wiiuse code force an out-of-tree build:
> https://github.com/supertuxkart/stk-code/blob/master/lib/wiiuse/cmake/cmake-4.0.0-modules/RequireOutOfSourceBuild.cmake#L41
> 
> Fixes a build error not yet caught by the autobuilders:
> 
> -- Configuring WiiUse version 0.15.5
> CMake Error at lib/wiiuse/cmake/cmake-4.0.0-modules/RequireOutOfSourceBuild.cmake:41 (message):
>   You must set a binary directory that is different from your source
>   directory.  You might consider
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
>  package/supertuxkart/supertuxkart.mk | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/package/supertuxkart/supertuxkart.mk b/package/supertuxkart/supertuxkart.mk
> index 1f9ad4102b..6bdd512eac 100644
> --- a/package/supertuxkart/supertuxkart.mk
> +++ b/package/supertuxkart/supertuxkart.mk
> @@ -44,6 +44,7 @@ SUPERTUXKART_CONF_OPTS = -DBUILD_SHARED_LIBS=OFF \
>  ifeq ($(BR2_PACKAGE_BLUEZ5_UTILS),y)
>  SUPERTUXKART_DEPENDENCIES += bluez5_utils
>  SUPERTUXKART_CONF_OPTS += -DUSE_WIIUSE=ON -DUSE_SYSTEM_WIIUSE=ON
> +SUPERTUXKART_SUPPORTS_IN_SOURCE_BUILD = NO

I was not really sure if putting this variable within a conditional was
a good idea. Normally a package either requires out-of-tree build or
doesn't care, and it's probably the first time we have a package that
sometimes requires it, sometimes doesn't. But as it reflects the
reality, I've applied your patch as-is. We'll see if other maintainers
disagree, which I would totally understand.

Thanks!

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:[~2023-07-22 21:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-16 13:55 [Buildroot] [PATCH 1/1] package/supertuxkart: fix build with bluetooth enabled Bernd Kuhls
2023-07-22 21:28 ` Thomas Petazzoni via buildroot [this message]
2023-08-29 20:00 ` Peter Korsgaard

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=20230722232853.29d39f2c@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=romain.naour@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox