[Buildroot] How to regenerate zImage?

[Buildroot] How to regenerate zImage?

[Woody Wu]

After I made any small changes in kernel source, I can force the kernel
to be rebuilt by removing the .stamp_built under the
output/build/linux-version directory.  But, it's strange that the
output/zImage file always not get recreated or rebuilt.

How should I force the buildroot to regenerate the zImage file for me?
Thanks.

-- 
woody
I can't go back to yesterday - because I was a different person then.

[Buildroot] How to regenerate zImage?

[Thomas Petazzoni]

Dear Woody Wu,

On Tue, 20 Nov 2012 08:17:54 +0000 (UTC), Woody Wu wrote:
> After I made any small changes in kernel source, I can force the kernel
> to be rebuilt by removing the .stamp_built under the
> output/build/linux-version directory.  But, it's strange that the
> output/zImage file always not get recreated or rebuilt.
> 
> How should I force the buildroot to regenerate the zImage file for me?

make linux-rebuild

However, note that making changing to the source code anywhere in
output/build/... is a really stupid idea, as all those changes will be
lost next time you do 'make clean'.

Best regard,s

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] How to regenerate zImage?

[Woody Wu]

On 2012-11-20, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com>
wrote:
> Dear Woody Wu,
>
> On Tue, 20 Nov 2012 08:17:54 +0000 (UTC), Woody Wu wrote:
>> After I made any small changes in kernel source, I can force the
>> kernel to be rebuilt by removing the .stamp_built under the
>> output/build/linux-version directory.  But, it's strange that the
>> output/zImage file always not get recreated or rebuilt.
>> 
>> How should I force the buildroot to regenerate the zImage file for
>> me?
>
> make linux-rebuild
Thanks, I will try.

>
> However, note that making changing to the source code anywhere in
> output/build/... is a really stupid idea, as all those changes will be
> lost next time you do 'make clean'.
>
Yes, I agree this is stupid. So I also really like to know whta's the
best practice to do this kind of work. Would you be so kind to have a
introduction or point me to a docment? Thanks


-- 
woody
I can't go back to yesterday - because I was a different person then.

[Buildroot] How to regenerate zImage?

[Woody Wu]

On 2012-11-20, Woody Wu
<narkewoody@gmail.com> wrote:
>> However, note that making changing to the source code anywhere in
>> output/build/... is a really stupid idea, as all those changes will
>> be lost next time you do 'make clean'.
>>
> Yes, I agree this is stupid. So I also really like to know whta's the
> best practice to do this kind of work. Would you be so kind to have a
> introduction or point me to a docment? Thanks
>

Hi, Thomas

Would you be so kind to draw a comment on this?


-- 
woody
I can't go back to yesterday - because I was a different person then.

[Buildroot] How to regenerate zImage?

[Thomas Petazzoni]

Dear Woody Wu,

On Tue, 20 Nov 2012 11:24:36 +0000 (UTC), Woody Wu wrote:

> > However, note that making changing to the source code anywhere in
> > output/build/... is a really stupid idea, as all those changes will be
> > lost next time you do 'make clean'.
> >
> Yes, I agree this is stupid. So I also really like to know whta's the
> best practice to do this kind of work. Would you be so kind to have a
> introduction or point me to a docment? Thanks

Two solutions:

 *) Do the build of the component you're actively working on outside of
    Buildroot. Typically, when I do kernel hacking, I do it outside of
    Buildroot, and I use Buildroot only as a final integration
    mechanism, to make sure that the system build process is
    reproducible. But not during development.

 *) Use the OVERRIDE_SRCDIR mechanism, as documented in
    http://www.elinux.org/images/2/2a/Using-buildroot-real-project.pdf,
    slide 41.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] How to regenerate zImage?

[Thomas Petazzoni]

Dear Woody Wu,

Please do not reply to me directly: always keep the list Cc'ed.

On Mon, 26 Nov 2012 15:32:52 +0800, Woody Wu wrote:
> > Two solutions:
> >
> >  *) Do the build of the component you're actively working on outside of
> >     Buildroot. Typically, when I do kernel hacking, I do it outside of
> >     Buildroot, and I use Buildroot only as a final integration
> >     mechanism, to make sure that the system build process is
> >     reproducible. But not during development.
> >
> >  *) Use the OVERRIDE_SRCDIR mechanism, as documented in
> >     http://www.elinux.org/images/2/2a/Using-buildroot-real-project.pdf,
> >     slide 41.
> >
> > Best regards,
> >
> > Thomas
> 
> Thanks for the excellent slides.  But I don't understand, where to
> input the "LINUX_OVERRIDE_SRCDIR=/my/path/of/linux".  Did I miss
> something?

You should put it in a file called "local.mk" at the root of the
Buildroot sources directory. Note that "local.mk" is the default
name/location, you can tune that using BR2_PACKAGE_OVERRIDE_FILE.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] How to regenerate zImage?

[Woody Wu]

On 2012-11-26, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com>
wrote:
> Dear Woody Wu,
>
> Please do not reply to me directly: always keep the list Cc'ed.
>

Sorry, I will stick to the list only.

> On Mon, 26 Nov 2012 15:32:52 +0800, Woody Wu wrote:
>> > Two solutions:
>> >
>> >  *) Do the build of the component you're actively working on
>> >  outside of Buildroot. Typically, when I do kernel hacking, I do it
>> >  outside of Buildroot, and I use Buildroot only as a final
>> >  integration mechanism, to make sure that the system build process
>> >  is reproducible. But not during development.
>> >
>> >  *) Use the OVERRIDE_SRCDIR mechanism, as documented in
>> >  http://www.elinux.org/images/2/2a/Using-buildroot-real-project.pdf,
>> >  slide 41.
>> >
>> > Best regards,
>> >
>> > Thomas
>> 
>> Thanks for the excellent slides.  But I don't understand, where to
>> input the "LINUX_OVERRIDE_SRCDIR=/my/path/of/linux".  Did I miss
>> something?
>
> You should put it in a file called "local.mk" at the root of the
> Buildroot sources directory. Note that "local.mk" is the default
> name/location, you can tune that using BR2_PACKAGE_OVERRIDE_FILE.
>

Many thanks.  I also want to do the same thing for the uboot, but I am
not certain what's the correct package name for it.  Should I use
UBOOT_OVERRIDE_SRCDIR or BOOT_OVERRIDE_SRCDIR? Thanks.

-- woody I can't go back to yesterday - because I was a different person
then.

[Buildroot] How to regenerate zImage?

[Thomas Petazzoni]

Dear Woody Wu,

On Tue, 27 Nov 2012 01:57:46 +0000 (UTC), Woody Wu wrote:

> Many thanks.  I also want to do the same thing for the uboot, but I am
> not certain what's the correct package name for it.  Should I use
> UBOOT_OVERRIDE_SRCDIR or BOOT_OVERRIDE_SRCDIR? Thanks.

The package is in boot/uboot/. The name of the package is the name of
the directory, so 'uboot', which should be uppercased to UBOOT.
Therefore:

	UBOOT_OVERRIDE_SRCDIR

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com