Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] tslib broken
Date: Fri, 17 Apr 2009 07:00:19 +0200	[thread overview]
Message-ID: <20090417070019.72d26189@hcegtvedt> (raw)
In-Reply-To: <49E75DDE.60605@carallon.com>

On Thu, 16 Apr 2009 17:33:34 +0100
Will Wagner <will_wagner@carallon.com> wrote:

<snipp>

> Index: package/tslib/tslib.mk
> ===================================================================
> --- package/tslib/tslib.mk	(revision 25500)
> +++ package/tslib/tslib.mk	(working copy)
> @@ -15,8 +15,25 @@
>  TSLIB_CONF_OPT = \
>  	--enable-shared	\
>  	--prefix=/usr	\
> -	--sysconfdir=/etc
> +	--sysconfdir=/etc \
> +	--disable-linear-h2200 \
> +	--disable-ucb1x00 \
> +	--disable-corgi \
> +	--disable-collie \
> +	--disable-h3600 \
> +	--disable-mk712 \
> +	--disable-arctic2 \
> +	--enable-input
> 

Looks sane, as long as nobody uses the specific old style touch
interfaces. AFAIK /dev/input/event is the way to go these days.
 
>  TSLIB_DEPENDENCIES = uclibc
>  
>  $(eval $(call AUTOTARGETS,package,tslib))
> +	
> +$(TSLIB_HOOK_POST_EXTRACT):
> +	-rm package/tslib/tslib-1.0-absbit.patch
> +	-rm
> package/tslib/tslib-1.0-remove-return-on-error-from-check-df.patch

Huh? This looks wrong. Do you mean to remove .orig patch files from the
extracted directory? If so, please refresh the patches using quilt:

QUILT_DIFF_OPTS="-p --ignore-blank-lines --strip-trailing-cr" quilt
refresh -p ab --no-timestamps --no-index

My preferred way of making patches for Buildroot that are smooth to
source control.

<snipp>

-- 
Best regards,
Hans-Christian Egtvedt

      reply	other threads:[~2009-04-17  5:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 16:33 [Buildroot] tslib broken Will Wagner
2009-04-17  5:00 ` Hans-Christian Egtvedt [this message]

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=20090417070019.72d26189@hcegtvedt \
    --to=hans-christian.egtvedt@atmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox