From: Joshua Henderson <joshua.henderson@microchip.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] qt5 add qmake.conf.in for eglfs
Date: Wed, 8 Nov 2017 11:42:35 -0700 [thread overview]
Message-ID: <52578484-a127-0727-e677-49c17058cc17@microchip.com> (raw)
In-Reply-To: <1510165263-7599-1-git-send-email-giulio.benetti@micronovasrl.com>
Giulio,
On 11/08/2017 11:21 AM, Giulio Benetti wrote:
> EGLFS_DEVICE_INTEGRATION = eglfs_* doesn't work correctly with previous patch
> EGLFS_DEVICE_INTEGRATION = eglfs_viv/eglfs_* must be written before include(../common/linux_device_post.conf)
>
> Starting from qmake.conf.in,
> generate qmake.conf substituting @EGLFS_DEVICE@ with eglfs_viv or eglfs_mali
> according to Package selection
>
---
Tip: In the future, put 3 dashes right here so the revision notes, and any notes
in general you want to include in the email, are not included in the final
commit log. You can apply the generated email yourself to a clean tree and see
that anything below the 3 dashes is dropped.
> Changes v1 -> v2:
>
> * Moved qmake.conf to qmake.conf.in
> * Added @EGLFS_DEVICE@ placeholder into qmake.conf.in
> * Modified QT5BASE_CONFIGURE_QMAKE_CONFIG to use sed
>
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>
> ---
...
Josh
next prev parent reply other threads:[~2017-11-08 18:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 18:21 [Buildroot] [PATCH v2 1/2] qt5 add qmake.conf.in for eglfs Giulio Benetti
2017-11-08 18:21 ` [Buildroot] [PATCH v2 2/2] add qmake.conf eglfs_mali option Giulio Benetti
2017-11-08 22:39 ` Arnout Vandecappelle
2017-11-08 22:45 ` Giulio Benetti
2017-11-08 18:42 ` Joshua Henderson [this message]
2017-11-08 18:52 ` [Buildroot] [PATCH v2 1/2] qt5 add qmake.conf.in for eglfs Giulio Benetti
2017-11-08 18:53 ` Giulio Benetti
2017-11-08 20:03 ` Joshua Henderson
2017-11-08 21:50 ` Giulio Benetti
2017-11-08 22:30 ` Arnout Vandecappelle
2017-11-08 22:43 ` Giulio Benetti
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=52578484-a127-0727-e677-49c17058cc17@microchip.com \
--to=joshua.henderson@microchip.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