Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Picard <davepiq@yahoo.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Qwt package : added dependency to Qt5 besides Qt.
Date: Mon, 25 Jan 2016 15:40:52 +0100	[thread overview]
Message-ID: <56A633F4.7080201@yahoo.fr> (raw)
In-Reply-To: <56A5E74A.4050002@yahoo.fr>

Arnout, is that what you mean by "automatic dependency" ?

qwt.mk
------

ifeq ($(BR2_PACKAGE_QT),y)
QWT_DEPENDENCIES += qt libgles libegl
endif
ifeq ($(BR2_PACKAGE_QT5BASE),y)
QWT_DEPENDENCIES += qt5base libgles
QT5_MAKE = $(HOST_DIR)/usr/bin/qmake -spec 
$(HOST_DIR)/mkspecs/devices/linux-buildroot-g++
endif


Config.in
---------

config BR2_PACKAGE_QWT_OPENGL
         bool "OpenGL support"
         depends on BR2_PACKAGE_HAS_LIBGLES
         depends on BR2_PACKAGE_HAS_LIBEGL



Le 25/01/2016 10:13, David Picard a ?crit :
> Hi,
>
> I could implement Yann's suggestions. The Config.in is more symetric,
> and I dropped the comment about SVG (no more recursive deps).
>
> In the OpenGL section, I can understand :
> depends on BR2_PACKAGE_QT_OPENGL_ES || BR2_PACKAGE_QT5BASE_OPENGL_LIB
>
> But I am afraid that I won't be able to make the automatic dependency in
> the .mk file, as Arnout suggests, because I have no idea of how to do
> it. Would you have an example in mind that I could have a look at ? Or
> will it do it as is ?
>
> When I am done, should I submit the patch as a new patch ? Or do you
> have a different procedure for revised patches ?
>
> Thanks,
> David.
>
>
>
> Le 24/01/2016 02:09, Arnout Vandecappelle a ?crit :
>> On 22-01-16 19:19, Yann E. MORIN wrote:
>>> David, All,
>>>
>>> On 2016-01-22 18:44 +0100, David Picard spake thusly:
>> [snip]
>>>> @@ -21,10 +23,14 @@ config BR2_PACKAGE_QWT_OPENGL
>>>>       bool "OpenGL support"
>>>>       depends on BR2_PACKAGE_HAS_LIBGLES
>>>>       depends on BR2_PACKAGE_HAS_LIBEGL
>>>> -    select BR2_PACKAGE_QT_OPENGL_ES
>>>> +    select BR2_PACKAGE_QT_OPENGL_ES if BR2_PACKAGE_QT
>>>> +    select BR2_PACKAGE_QT5BASE_OPENGL_LIB if BR2_PACKAGE_QT5BASE
>>>
>>> BR2_PACKAGE_QT5BASE_OPENGL_LIB depends on BR2_PACKAGE_QT5BASE_OPENGL, so
>>> it should have been selected too.
>>>
>>> However, I'm a bit worried about the complexity here, and I'd rather
>>> that we depend on such support rather than select it. So I'd prefer to
>>> see:
>>>
>>>      depends on BR2_PACKAGE_QT_OPENGL_ES ||
>>> BR2_PACKAGE_QT5BASE_OPENGL_LIB
>>
>>   In that case, it can probably be removed completely and turned into an
>> automatic dependency (i.e. just in the .mk file).
>>
>>   I also wouldn't bother with legacy handling when this symbol is
>> removed. The
>> legacy .config file will already contain BR2_PACKAGE_QT_OPENGL_ES, so
>> once the
>> handling is automatic, you just have to run 'make oldconfig' and it
>> will Just
>> Work (TM).
>>
>>
>>   Regards,
>>   Arnout
>>
>> [snip]
>>
>>
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  parent reply	other threads:[~2016-01-25 14:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 17:44 [Buildroot] [PATCH 1/2] Update for 2015.11.1 David Picard
2016-01-22 17:44 ` [Buildroot] [PATCH 2/2] Qwt package : added dependency to Qt5 besides Qt David Picard
2016-01-22 18:19   ` Yann E. MORIN
     [not found]     ` <56A34AFC.7070908@yahoo.fr>
2016-01-23 13:32       ` Yann E. MORIN
2016-01-24  1:09     ` Arnout Vandecappelle
2016-01-24 16:20       ` Yann E. MORIN
2016-01-25  9:13       ` David Picard
2016-01-25  9:25         ` David Picard
2016-01-25 14:40         ` David Picard [this message]
2016-01-22 17:50 ` [Buildroot] [PATCH 1/2] Update for 2015.11.1 Yann E. MORIN

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=56A633F4.7080201@yahoo.fr \
    --to=davepiq@yahoo.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