All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] update on a file in tslib not reflected after doing "Make"
Date: Tue, 15 Dec 2009 09:18:36 +0100	[thread overview]
Message-ID: <874onsr6oz.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <ed7750810912142330nbfb9fb5q2b261926c6d2b4c2@mail.gmail.com> (Stanley's message of "Tue, 15 Dec 2009 15:30:06 +0800")

>>>>> "Stanley" == Stanley  <eva2002@gmail.com> writes:

 Stanley> Hi all,

 Stanley> I am new to embedded world and this is the first time using
 Stanley> buildroot.  I am currently trying to solve a problem in one of
 Stanley> the files (input-raw.c) on tslib. However after modify/patch
 Stanley> the file, I do a "make" in main buildroot directory. However
 Stanley> the changes did not reflected (tested by adding a few texts in
 Stanley> already existing printf statement).

 Stanley> Here is what I did.

 Stanley> 1) delete "tslib" folder from "build_arm" folder.

If you have a build_arm folder, then you are not using the latest
release. Any reason why you are not using 2009.11?

So if I get you right, you want to add a custom patch to tslib? You can
either just place it in package/tslib together with the other patches
(make sure you name it tslib-1.0-<something>.patch), or for a quick test
just build tslib without changing anything, and then afterwards go to
output/build/tslib-1.0, change what you need to change and then remove
the stamp file (.stamp_built).

Once that is done you can just rerun make from the toplevel buildroot
dir and tslib should get rebuilt/reinstalled.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-12-15  8:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15  7:30 [Buildroot] update on a file in tslib not reflected after doing "Make" Stanley
2009-12-15  8:18 ` Peter Korsgaard [this message]
2009-12-15  8:27 ` Thomas Petazzoni
2009-12-16  4:30   ` Stanley
2009-12-16 20:35     ` Peter Korsgaard
2009-12-17  7:35       ` Thomas Petazzoni
2009-12-17 10:45         ` Stanley
2009-12-21  4:39         ` Stanley

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=874onsr6oz.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 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.