> On Sep 28, 2015, at 17:04 , Robert Nelson <[email protected]> wrote:
> 
> On Mon, Sep 28, 2015 at 11:51 PM, Rick Mann <[email protected]> wrote:
>> 
>>> On Sep 28, 2015, at 16:45 , Robert Nelson <[email protected]> wrote:
>>> 
>>> On Mon, Sep 28, 2015 at 11:42 PM, Rick Mann <[email protected]> wrote:
>>>> 
>>>>> On Sep 28, 2015, at 16:34 , Robert Nelson <[email protected]> wrote:
>>>>> 
>>>>>> Your script worked great!
>>>>>> 
>>>>>> Now, if I make a change to the source and want to rebuild and 
>>>>>> re-generate the .debs, what do I do?
>>>>> 
>>>>> ./tools/rebuild_deb.sh
>>>> 
>>>> Hmm, that seems to do a LOT of work. It re-presented menuconfig, which I 
>>>> just exited, and then it cleaned a bunch of directories, tarred up 
>>>> linux-upstream again, and is rebuilding everything.
>>>> 
>>>> I just want to recompile the one file I changed (or any that depended on 
>>>> it, but this was a .c file), and have it re-build the .debs, etc.
>>> 
>>> but... it's not redoing the "KERNEL" directory.. ;)
>>> 
>>> upsteam "make deb-pkg" does all that extra stuff, save your self by
>> 
>> So, would I just
>> 
>> $ cd KERNEL
>> $ make
>> $ make deb-pkg
> 
> That's what: "./tools/rebuild_deb.sh" does..

Yeah, I just tried its make invocation...rebuilding everything again. Even with 
ccache, this would be too much.

> 
>> 
>>> install "ccache" and enabling 2GB for ~/.ccache
>> 
>> Okay, I'll look into this. Seems like a bandaid over a broken build, if one 
>> can't just analyze the dependencies and skip build steps that don't need to 
>> happen.
> 
> it's just for "deb-pkg" packaging script... the "./tools/rebuild.sh"
> that just calls make is more sane and would have just updated the one

Ah, okay, I'll try that next.

-- 
Rick Mann
[email protected]


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to