From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libsexy
Date: Wed, 27 Aug 2008 13:19:16 -0700 (PDT) [thread overview]
Message-ID: <20080827201916.8DE79F8012@busybox.net> (raw)
Author: jacmet
Date: 2008-08-27 13:19:15 -0700 (Wed, 27 Aug 2008)
New Revision: 23258
Log:
libsexy: fix long help text lines
Make it depend on libgtk2 while we're at it.
Modified:
trunk/buildroot/package/libsexy/Config.in
Changeset:
Modified: trunk/buildroot/package/libsexy/Config.in
===================================================================
--- trunk/buildroot/package/libsexy/Config.in 2008-08-27 20:19:12 UTC (rev 23257)
+++ trunk/buildroot/package/libsexy/Config.in 2008-08-27 20:19:15 UTC (rev 23258)
@@ -1,6 +1,10 @@
config BR2_PACKAGE_LIBSEXY
bool "libsexy"
+ depends on BR2_PACKAGE_LIBGTK2
help
- libsexy is a collection of GTK+ widgets that extend the functionality of such standard widgets as GtkEntry and GtkLabel by subclassing them and working around the limitations of the widgets.
+ libsexy is a collection of GTK+ widgets that extend the
+ functionality of such standard widgets as GtkEntry and
+ GtkLabel by subclassing them and working around the
+ limitations of the widgets.
http://www.chipx86.com/wiki/Libsexy
next reply other threads:[~2008-08-27 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 20:19 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-23 17:48 [Buildroot] svn commit: trunk/buildroot/package/libsexy ulf at uclibc.org
2009-01-23 18:48 ` Peter Korsgaard
2009-01-23 21:06 ` Ulf Samuelsson
2009-01-27 0:26 ` Hamish Moffatt
2009-01-27 5:52 ` Peter Korsgaard
2009-01-24 6:44 jacmet at uclibc.org
2009-01-24 6:44 jacmet at uclibc.org
2009-01-26 6:18 ` Hans-Christian Egtvedt
2009-01-26 6:31 ` Peter Korsgaard
2009-01-26 6:30 jacmet 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=20080827201916.8DE79F8012@busybox.net \
--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