All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Laird <daniel.j.laird@nxp.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libgtk2
Date: Tue, 26 Aug 2008 06:32:13 -0700 (PDT)	[thread overview]
Message-ID: <19162136.post@talk.nabble.com> (raw)
In-Reply-To: <87k5e3gbne.fsf@macbook.be.48ers.dk>


I will amend the Config.in to do as suggested:
Config.in
select CUPS if ......

and

libgtk2.mk
ifeq ($(BR2_PACKAGE_CUPS),y)
	LIBGTK2_DEPENDENCIES_EXTRA = cups
endif

However this does raise the wider issue of what should be auto selected and
what should be chosen
IMHO I feel CUPS is not a necessary thing for GTK??
Therefore why is it being autoselected for X builds.
If someone wants cups then they should select it in their configuration
file.
Packages that compile differently due to the selection of another package
could use something like:

ifeq ($(BR2_PACKAGE_CUPS),y)
	........ (--enable-cups) or whatever
endif

This I think is far better than someone building X and GTK and finding their
build fails because of cups.  If they want it they should enable it.

Dan laird


-- 
View this message in context: http://www.nabble.com/svn-commit%3A-trunk-buildroot-package-libgtk2-tp19160871p19162136.html
Sent from the BuildRoot mailing list archive at Nabble.com.

  reply	other threads:[~2008-08-26 13:32 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 12:19 [Buildroot] svn commit: trunk/buildroot/package/libgtk2 laird at uclibc.org
2008-08-26 13:15 ` Peter Korsgaard
2008-08-26 13:32   ` Daniel Laird [this message]
2008-08-26 13:38     ` Peter Korsgaard
2008-08-26 14:04       ` Bernhard Reutner-Fischer
2008-08-26 14:07     ` Bernhard Reutner-Fischer
2008-08-26 14:54       ` Peter Korsgaard
2008-08-26 13:48   ` Bernhard Reutner-Fischer
2008-08-26 14:07     ` Peter Korsgaard
2008-08-26 14:11       ` Bernhard Reutner-Fischer
2008-08-26 14:13       ` Daniel Laird
2008-08-26 13:42 ` Ormund Williams
2008-08-26 13:49   ` Daniel Laird
  -- strict thread matches above, loose matches on Subject: below --
2009-01-18 10:57 ulf at uclibc.org
2009-01-18 11:05 ` Peter Korsgaard
2009-01-18 13:11   ` Sven Neumann
2009-01-18 13:43     ` Daniel Laird
2009-01-18 13:48     ` Peter Korsgaard
2009-01-14 22:11 ulf at uclibc.org
2009-01-15  8:36 ` Thomas Lundquist
2009-01-15 20:18   ` Ulf Samuelsson
2009-01-15 20:26     ` Peter Korsgaard
2009-01-15 20:37       ` Ulf Samuelsson
2008-12-31  9:35 jacmet at uclibc.org
2008-12-26 15:36 jacmet at uclibc.org
2008-12-26 15:36 jacmet at uclibc.org
2008-10-27  9:45 jacmet at uclibc.org
2008-10-18  7:00 jacmet at uclibc.org
2008-08-26 13:45 laird at uclibc.org
2008-07-08 10:09 ulf at uclibc.org
2008-07-07 11:09 ulf at uclibc.org
2008-07-06  6:25 ulf at uclibc.org
2007-02-01 19:20 andersen at uclibc.org
2007-01-17 11:27 jacmet at uclibc.org
2007-01-17  0:04 andersen at uclibc.org
2007-01-14 23:27 andersen at uclibc.org
2007-01-14 23:26 andersen 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=19162136.post@talk.nabble.com \
    --to=daniel.j.laird@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.