Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/stellarium: new package
Date: Mon, 5 Aug 2019 00:07:52 +0200	[thread overview]
Message-ID: <20190805000752.06b970bf@windsurf.home> (raw)
In-Reply-To: <20190804160432.19791-1-bernd.kuhls@t-online.de>

Hello Bernd,

On Sun,  4 Aug 2019 18:04:32 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:


> diff --git a/package/stellarium/Config.in b/package/stellarium/Config.in
> new file mode 100644
> index 0000000000..4232f9ed1a
> --- /dev/null
> +++ b/package/stellarium/Config.in
> @@ -0,0 +1,27 @@
> +config BR2_PACKAGE_STELLARIUM
> +	bool "stellarium"
> +	depends on BR2_PACKAGE_QT5
> +	depends on BR2_PACKAGE_QT5_GL_AVAILABLE
> +	depends on BR2_PACKAGE_HAS_LIBGL

Why do you have a depends on BR2_PACKAGE_HAS_LIBGL in addition to
BR2_PACKAGE_QT5_GL_AVAILABLE ? The Qt OpenGL support works with both
full OpenGL or OpenGL ES. Is there something in stellarium that limits
it to full OpenGL ?

> +	select BR2_PACKAGE_QT5BASE_CONCURRENT
> +	select BR2_PACKAGE_QT5BASE_GUI
> +	select BR2_PACKAGE_QT5BASE_NETWORK
> +	select BR2_PACKAGE_QT5BASE_OPENGL
> +	select BR2_PACKAGE_QT5BASE_PRINTSUPPORT
> +	select BR2_PACKAGE_QT5BASE_WIDGETS
> +	select BR2_PACKAGE_QT5LOCATION
> +	select BR2_PACKAGE_QT5MULTIMEDIA
> +	select BR2_PACKAGE_QT5SCRIPT if BR2_PACKAGE_QT5_JSCORE_AVAILABLE
> +	select BR2_PACKAGE_QT5SERIALPORT if BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_6

So how does it work when BR2_PACKAGE_QT5_JSCORE_AVAILABLE or
BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_6 are not 'y' ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-08-04 22:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04 16:04 [Buildroot] [PATCH 1/1] package/stellarium: new package Bernd Kuhls
2019-08-04 22:07 ` Thomas Petazzoni [this message]
2019-08-05  5:38   ` Bernd Kuhls
2019-08-05 20:42     ` 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=20190805000752.06b970bf@windsurf.home \
    --to=thomas.petazzoni@bootlin.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