Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Best way to add custom step
@ 2008-02-11 15:13 Will Wagner
  2008-02-11 15:26 ` Ulf Samuelsson
  0 siblings, 1 reply; 4+ messages in thread
From: Will Wagner @ 2008-02-11 15:13 UTC (permalink / raw)
  To: buildroot

Hi All,

I need to add a custom step to my build process after the linux image is 
built into the binaries directory. I was wondering about what was the 
best way to go about this.

I could add my changes to the top level makefile or to the 
target\linux\Makefile.in file. Is one way better than the other? Is 
there a better way of doing this?

Thanks,

Will
-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Senior Project Engineer                  Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] Best way to add custom step
  2008-02-11 15:13 [Buildroot] Best way to add custom step Will Wagner
@ 2008-02-11 15:26 ` Ulf Samuelsson
  2008-02-12  9:17   ` Will Wagner
  0 siblings, 1 reply; 4+ messages in thread
From: Ulf Samuelsson @ 2008-02-11 15:26 UTC (permalink / raw)
  To: buildroot

----- Original Message ----- 
From: "Will Wagner" <will_wagner@carallon.com>
To: <buildroot@uclibc.org>
Sent: Monday, February 11, 2008 4:13 PM
Subject: [Buildroot] Best way to add custom step


> Hi All,
> 
> I need to add a custom step to my build process after the linux image is 
> built into the binaries directory. I was wondering about what was the 
> best way to go about this.
> 
> I could add my changes to the top level makefile or to the 
> target\linux\Makefile.in file. Is one way better than the other? Is 
> there a better way of doing this?
> 
> Thanks,
> 


If it is board specific, then it makes more sense to put it
in target/device and let the target depend on the linux binary.

What is the custom  step?



Best Regards
Ulf Samuelsson

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] Best way to add custom step
  2008-02-11 15:26 ` Ulf Samuelsson
@ 2008-02-12  9:17   ` Will Wagner
  2008-02-12  9:24     ` Ulf Samuelsson
  0 siblings, 1 reply; 4+ messages in thread
From: Will Wagner @ 2008-02-12  9:17 UTC (permalink / raw)
  To: buildroot

>> I need to add a custom step to my build process after the linux image is 
>> built into the binaries directory. I was wondering about what was the 
>> best way to go about this.
>>
>> I could add my changes to the top level makefile or to the 
>> target\linux\Makefile.in file. Is one way better than the other? Is 
>> there a better way of doing this?
>>
>> Thanks,
>>
> 
> 
> If it is board specific, then it makes more sense to put it
> in target/device and let the target depend on the linux binary.

Thanks, after looking at it some more I realised this.

> 
> What is the custom  step?

Need to wrap the kernel image with some extra bytes that include crc and 
size so that nandboot accepts it.

> 
> 
> 
> Best Regards
> Ulf Samuelsson

-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Senior Project Engineer                  Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] Best way to add custom step
  2008-02-12  9:17   ` Will Wagner
@ 2008-02-12  9:24     ` Ulf Samuelsson
  0 siblings, 0 replies; 4+ messages in thread
From: Ulf Samuelsson @ 2008-02-12  9:24 UTC (permalink / raw)
  To: buildroot

>>> I need to add a custom step to my build process after the linux image is 
>>> built into the binaries directory. I was wondering about what was the 
>>> best way to go about this.
>>>
>>> I could add my changes to the top level makefile or to the 
>>> target\linux\Makefile.in file. Is one way better than the other? Is 
>>> there a better way of doing this?
>>>
>>> Thanks,
>>>
>> 
>> 
>> If it is board specific, then it makes more sense to put it
>> in target/device and let the target depend on the linux binary.
> 
> Thanks, after looking at it some more I realised this.
> 
>> 
>> What is the custom  step?
> 
> Need to wrap the kernel image with some extra bytes that include crc and 
> size so that nandboot accepts it.
> 
>> 


Any plans to build NAND boot within Buildroot?

What is NAND boot?

Best Regards
Ulf Samuelsson

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-02-12  9:24 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-11 15:13 [Buildroot] Best way to add custom step Will Wagner
2008-02-11 15:26 ` Ulf Samuelsson
2008-02-12  9:17   ` Will Wagner
2008-02-12  9:24     ` Ulf Samuelsson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox