All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Maxim Kochetkov via buildroot <buildroot@buildroot.org>
Cc: Maxim Kochetkov <fido_max@inbox.ru>
Subject: Re: [Buildroot] [PATCH 1/1] qt5: enable jscore/qt5declarative support for riscv
Date: Wed, 3 Apr 2024 23:15:41 +0200	[thread overview]
Message-ID: <20240403231541.5b862c85@windsurf> (raw)
In-Reply-To: <20230920060831.71857-1-fido_max@inbox.ru>

Hello Maxim,

On Wed, 20 Sep 2023 09:08:31 +0300
Maxim Kochetkov via buildroot <buildroot@buildroot.org> wrote:

> Signed-off-by: Maxim Kochetkov <fido_max@inbox.ru>
> ---
>  package/qt5/Config.in | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/qt5/Config.in b/package/qt5/Config.in
> index f1b16ff39b..e15d3a5005 100644
> --- a/package/qt5/Config.in
> +++ b/package/qt5/Config.in
> @@ -7,7 +7,7 @@ config BR2_PACKAGE_QT5_JSCORE_AVAILABLE
>  	bool
>  	default y
>  	# Javascript engine is only available on certain architectures
> -	depends on BR2_arm || BR2_aarch64 || BR2_i386 || BR2_x86_64 || BR2_mipsel || BR2_arc
> +	depends on BR2_arm || BR2_aarch64 || BR2_i386 || BR2_x86_64 || BR2_mipsel || BR2_arc || BR2_riscv

Thanks for the patch and sorry for the super long delay in getting back
to you. Could you provide a bit of details regarding since which
version is RISC-V supported by JSCore ?

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:[~2024-04-03 21:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20  6:08 [Buildroot] [PATCH 1/1] qt5: enable jscore/qt5declarative support for riscv Maxim Kochetkov via buildroot
2024-04-03 21:15 ` 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=20240403231541.5b862c85@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fido_max@inbox.ru \
    --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.