From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] update on a file in tslib not reflected after doing "Make"
Date: Tue, 15 Dec 2009 09:27:51 +0100 [thread overview]
Message-ID: <20091215092751.7d9a48fe@surf> (raw)
In-Reply-To: <ed7750810912142330nbfb9fb5q2b261926c6d2b4c2@mail.gmail.com>
Le Tue, 15 Dec 2009 15:30:06 +0800,
Stanley <eva2002@gmail.com> a ?crit :
> Anyone knows how to resolve this problem?
Let Buildroot does its compilation process to the end.
Then, make your modifications to build_arm/tslib-x.x/. Then, remove
the build_arm/tslib-x.x/.stamp_build file.
Re-run make.
This topic is covered in Buildroot documentation, see
docs/buildroot.html.
Cheers,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-12-15 8:27 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
2009-12-15 8:27 ` Thomas Petazzoni [this message]
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=20091215092751.7d9a48fe@surf \
--to=thomas.petazzoni@free-electrons.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.