Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/webkit
Date: Wed, 28 Jan 2009 08:58:09 +0100	[thread overview]
Message-ID: <87fxj3x3ou.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090128081026.55f4a8f8@hcegtvedt> (Hans-Christian Egtvedt's message of "Wed\, 28 Jan 2009 08\:10\:26 +0100")

>>>>> "Hans-Christian" == Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com> writes:

Hi,

 >> --- trunk/buildroot/package/webkit/Config.in	2009-01-27
 >> 15:02:40 UTC (rev 25080) +++
 >> trunk/buildroot/package/webkit/Config.in	2009-01-27 15:10:08
 >> UTC (rev 25081) @@ -1,5 +1,7 @@ config BR2_PACKAGE_WEBKIT
 >> bool "webkit"
 >> +	depends on BR2_INSTALL_LIBSTDCPP
 >> +	depends on BR2_USE_WCHAR

 Hans-Christian> Do you need C++/WCHAR for webkit as well, or only
 Hans-Christian> icu? If it is only icu then should not kconfig take
 Hans-Christian> care of this dependency since selecting icu package
 Hans-Christian> will not be possible?

Well, you could certainly argue that it should, but the fact is that
Kconfig doesn't take dependencies into consideration when it handles
selects, E.G. nothing stops you from select'ing a package with
unforfilled deps.

Webkit is furthermore C++ code, so that part is atleast correct.

 >> select BR2_PACKAGE_LIBGTK2
 >> select BR2_PACKAGE_ICU
 >> select BR2_PACKAGE_CURL
 >> @@ -11,3 +13,5 @@
 >> 
 >> http://webkit.org/
 >> 
 >> +comment "webkit requires a toolchain with C++ support and WCHAR
 >> enabled"
 >> +	depends on !BR2_INSTALL_LIBSTDCPP || !BR2_USE_WCHAR
 >> 

 Hans-Christian> And then make a depends on package icu instead?

No, I don't think hiding applications until you by accident manages to
enable all the required libraries is a good idea.

Applications should select their library dependencies and depend (with
a comment) on toolchain features.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-01-28  7:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 15:10 [Buildroot] svn commit: trunk/buildroot/package/webkit jacmet at uclibc.org
2009-01-28  7:10 ` Hans-Christian Egtvedt
2009-01-28  7:58   ` Peter Korsgaard [this message]
2009-01-28  8:06     ` Hans-Christian Egtvedt
2009-01-28  8:14       ` Peter Korsgaard
2009-01-28  8:19         ` Hans-Christian Egtvedt
2009-01-28  8:30           ` Peter Korsgaard
2009-01-28  8:39             ` Hans-Christian Egtvedt
  -- strict thread matches above, loose matches on Subject: below --
2009-01-27 15:02 jacmet at uclibc.org
2009-01-27 15:02 jacmet at uclibc.org
2009-01-23 17:49 ulf at uclibc.org
2009-01-27  0:27 ` Hamish Moffatt
2009-01-27  8:25   ` Daniel Laird
2009-01-27  8:57     ` Peter Korsgaard
2009-01-27 10:15       ` Daniel James Laird
2009-01-27 15:06         ` Peter Korsgaard
2008-04-24 13:22 ninevoltz at uclibc.org

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=87fxj3x3ou.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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