From: Pierre Le Magourou <pierre.lemagourou@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] qt5cinex: Add new Qt5CinematicExperience package.
Date: Wed, 17 Dec 2014 10:37:40 +0100 [thread overview]
Message-ID: <54914EE4.60103@openwide.fr> (raw)
In-Reply-To: <20141214230211.GH4121@free.fr>
Yann,
> Thank you for your contribution. Sorry for the delay in reviewing this
> patch; here is my review...
>
I have modified my patch taking into account what you said in your
review. I will send a new patch once I received feedback concerning
where to put the Qt binary file, but I have to clarify something
concerning arm dependency before.
[--SNIP--]
>> +if BR2_PACKAGE_QT5CINEX
>> +
>> +config BR2_PACKAGE_QT5CINEX_RPI
>> + bool "RaspberryPI Edition"
>
> This should at least "depends on BR2_arm".
The name of the upstream software is confusing here, it is called
"RaspberryPI edition" but it can also be run on any other platform
that have Qt5 installed. I run it on my laptop without any problem.
So I would say that this package does not need to depend on BR2_arm.
I decided to modify the name of this option to "High Definition
Edition" instead because the difference with the first option is
mainly the 1920x1080 resolution.
>
> Also, does it use either or both of rpi-userland or rpi-firmware at
> build time or at runtime?
In my understanding, this application is platform independent. It
only needs a functional Qt5 framework installed with
QT5GRAPHICALEFFECTS and does not use rpi-firmware nor rpi-userland.
The dependency to rpi-userland comes from the Qt5GraphicalEffect
package that needs BR2_PACKAGE_QT5_GL_AVAILABLE that will ask for
rpi-userland package to provide GLESv2 on RaspberryPi platform.
>
> If so, you should add proper dependencies, for example:
>
> - if build or runtime dependency, add in Config.in:
> config BR2_PACKAGE_QT5CINEX_RPI
> bool "RaspberryPI Edition"
> depends on BR2_PACKAGE_RPI_USERLAND
>
> - if runtime dependency, add in qt5cinex.mk:
> QT5CINEX_RPI_DEPENDENCIES += rpi-userland
>
> (but that's just an example.)
>
Regards.
--
Pierre Le Magourou
next prev parent reply other threads:[~2014-12-17 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 10:05 [Buildroot] [PATCH 1/1] qt5cinex: Add new Qt5CinematicExperience package pierre.lemagourou at openwide.fr
2014-12-14 23:02 ` Yann E. MORIN
2014-12-17 9:37 ` Pierre Le Magourou [this message]
2014-12-17 18:12 ` Yann E. MORIN
-- strict thread matches above, loose matches on Subject: below --
2015-01-07 14:22 pierre.lemagourou at openwide.fr
2015-01-07 20:39 ` 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=54914EE4.60103@openwide.fr \
--to=pierre.lemagourou@openwide.fr \
--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