From: ninevoltz at uclibc.org <ninevoltz@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/xstroke
Date: Thu, 24 Apr 2008 06:23:29 -0700 (PDT) [thread overview]
Message-ID: <20080424132329.0B95B3C863@busybox.net> (raw)
Author: ninevoltz
Date: 2008-04-24 06:23:28 -0700 (Thu, 24 Apr 2008)
New Revision: 21838
Log:
select docker with xstroke so xstroke has a place to live
Modified:
trunk/buildroot/package/xstroke/Config.in
trunk/buildroot/package/xstroke/xstroke.mk
Changeset:
Modified: trunk/buildroot/package/xstroke/Config.in
===================================================================
--- trunk/buildroot/package/xstroke/Config.in 2008-04-24 13:22:34 UTC (rev 21837)
+++ trunk/buildroot/package/xstroke/Config.in 2008-04-24 13:23:28 UTC (rev 21838)
@@ -1,5 +1,6 @@
config BR2_PACKAGE_XSTROKE
bool "xstroke"
+ select BR2_PACKAGE_DOCKER
default n
help
Handwriting recognition for X
Modified: trunk/buildroot/package/xstroke/xstroke.mk
===================================================================
--- trunk/buildroot/package/xstroke/xstroke.mk 2008-04-24 13:22:34 UTC (rev 21837)
+++ trunk/buildroot/package/xstroke/xstroke.mk 2008-04-24 13:23:28 UTC (rev 21838)
@@ -11,7 +11,7 @@
XSTROKE_INSTALL_TARGET = YES
XSTROKE_INSTALL_TARGET_OPT = DESTDIR=$(TARGET_DIR) install
-XSTROKE_DEPENDENCIES = uclibc docker
+XSTROKE_DEPENDENCIES = uclibc
$(eval $(call AUTOTARGETS,package,xstroke))
next reply other threads:[~2008-04-24 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 13:23 ninevoltz at uclibc.org [this message]
2008-04-24 13:53 ` [Buildroot] svn commit: trunk/buildroot/package/xstroke Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2008-04-24 14:25 ninevoltz at uclibc.org
2008-03-20 16:55 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=20080424132329.0B95B3C863@busybox.net \
--to=ninevoltz@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