From: Stanley <eva2002@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] update on a file in tslib not reflected after doing "Make"
Date: Thu, 17 Dec 2009 18:45:06 +0800 [thread overview]
Message-ID: <ed7750810912170245i63b752adtfb11fa836bc4e281@mail.gmail.com> (raw)
In-Reply-To: <20091217083547.5af1c179@surf>
Thanks for the reply.
In fact I did try both step ***separately*.
1) mod directly and remove.stamp_built file
2) create patches and rm the tslib folder and all related files (lib
file/folder, bin file) in the staging_dir.
however in both cases, the changes did not get reflected. I tried by greping
the mod statement.
eg. printf("xres = %d, yres = %d\n",...); << original
printf("test\n\n\n\n\nxres = %d, test yres = %d\n",...); << mod
then enter cmd: grep -r "test" <bin file> --> return nothing
enter cmd: grep -r "xres" <bin file> --> return 'xres = %d, yres = %d' only
Cheers,
Stanley
On Thu, Dec 17, 2009 at 3:35 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:
> Le Wed, 16 Dec 2009 21:35:16 +0100,
> Peter Korsgaard <jacmet@uclibc.org> a ?crit :
>
> > If you are putting new .patch files under package/tslib then you need
> > to rerun the patch step. The easiest way of doing this is simply to
> > delete the build dir (rm -rf output/build/tslib*)
>
> Yeah, basically:
>
> *) If you hack directly into output/build/tslib*, then you must remove
> the .stamp_built stamp file and run make again. This will restart
> the compile process at the build step of tslib (but will *not*
> reconfigure tslib, so if you made any modifications at the
> configure level, it won't work)
>
> *) If you add new patches to package/tslib/, then as Peter said, the
> easiest way is to rm -rf output/build/tslib.
>
> Cheers,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers and embedded Linux development,
> consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20091217/d7304cc1/attachment.htm>
next prev parent reply other threads:[~2009-12-17 10:45 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
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 [this message]
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=ed7750810912170245i63b752adtfb11fa836bc4e281@mail.gmail.com \
--to=eva2002@gmail.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