[Buildroot] Missing 'make install' option ?

[Buildroot] Missing 'make install' option ?

[Mark Jackson]

Correct me if I'm missing something here ...

After I've run a successful build the output/target directory contains
a copy of the target files.  Fine.

If I then, say, remove a package via 'make menuconfig', I have to then
perform a 'make dirclean; make' to generate a new set of target files.

This, of course, causes a re-compile of *everything* !!

Is this right ?  Seems a bit of overkill to blow away everything you've
just compiled, simply to remove some unwanted files.

Is there not a sort of 'make' option that:-

(a) deletes the output/target
(b) compiles any new packages added since the last build
(c) generates a new output/target tree

?

Thanks
Mark

[Buildroot] Missing 'make install' option ?

[Sven Neumann]

On Thu, 2009-10-15 at 10:38 +0100, Mark Jackson wrote:
> Correct me if I'm missing something here ...
> 
> After I've run a successful build the output/target directory contains
> a copy of the target files.  Fine.
> 
> If I then, say, remove a package via 'make menuconfig', I have to then
> perform a 'make dirclean; make' to generate a new set of target files.
> 
> This, of course, causes a re-compile of *everything* !!

You can use 'make package-clean' (with package substituted by the name
of the package) before deselecting the package. This will uninstall it
from staging and target areas.


Sven

[Buildroot] Missing 'make install' option ?

[Mark Jackson]

Sven Neumann wrote:
> On Thu, 2009-10-15 at 10:38 +0100, Mark Jackson wrote:
>> Correct me if I'm missing something here ...
>>
>> After I've run a successful build the output/target directory contains
>> a copy of the target files.  Fine.
>>
>> If I then, say, remove a package via 'make menuconfig', I have to then
>> perform a 'make dirclean; make' to generate a new set of target files.
>>
>> This, of course, causes a re-compile of *everything* !!
> 
> You can use 'make package-clean' (with package substituted by the name
> of the package) before deselecting the package. This will uninstall it
> from staging and target areas.

Okay ... but is there's no way to regenerate the output/target contents
without doing a 'make dirclean; make' ?

A sort of 'make install' which would:-

(a) delete the output/target contents
(b) copy target_skeleton to output/target
(c) run 'make install' on all selected packages (re-compiling if required)

I'd find that *most* useful !!

Mark

[Buildroot] Missing 'make install' option ?

[tike64 at gmail.com]

Mark Jackson wrote:
> A sort of 'make install' which would:-
> 
> (a) delete the output/target contents
> (b) copy target_skeleton to output/target
> (c) run 'make install' on all selected packages (re-compiling if required)
> 
> I'd find that *most* useful !!

I would also find it useful but, while we are waiting it, this might be of some 
value:

rm -rf output/build/.root output/target `find -name *target_installed`

I know, that even after that, make will do a lot of unneeded rebuilding but 
maybe not as much...

--

Timo

[Buildroot] Missing 'make install' option ?

[Sven Neumann]

On Thu, 2009-10-15 at 11:27 +0100, Mark Jackson wrote:

> A sort of 'make install' which would:-
> 
> (a) delete the output/target contents
> (b) copy target_skeleton to output/target
> (c) run 'make install' on all selected packages (re-compiling if required)

I would certainly not expect 'make install' to delete anything.


Sven

[Buildroot] Missing 'make install' option ?

[Mark Jackson]

Sven Neumann wrote:
> On Thu, 2009-10-15 at 11:27 +0100, Mark Jackson wrote:
> 
>> A sort of 'make install' which would:-
>>
>> (a) delete the output/target contents
>> (b) copy target_skeleton to output/target
>> (c) run 'make install' on all selected packages (re-compiling if required)
> 
> I would certainly not expect 'make install' to delete anything.

Okay ... so maybe the name is wrong ... something like:-

make target-clean; make target

??

[Buildroot] Missing 'make install' option ?

[Mark Jackson]

tike64 at gmail.com wrote:
> Mark Jackson wrote:
>> A sort of 'make install' which would:-
>>
>> (a) delete the output/target contents
>> (b) copy target_skeleton to output/target
>> (c) run 'make install' on all selected packages (re-compiling if
>> required)
>>
>> I'd find that *most* useful !!
> 
> I would also find it useful but, while we are waiting it, this might be
> of some value:
> 
> rm -rf output/build/.root output/target `find -name *target_installed`

Seems like a sledgehammer to crack a nut, and it still recompiles uclibc
*but* it's almost exactly what I was thinking about.

I'd still like a more formal approach to doing this, and I can't believe
that my requirements differ widely from most other developers !?!

Mark

[Buildroot] Missing 'make install' option ?

[Matuschka, Sebastian]

> Subject: Re: [Buildroot] Missing 'make install' option ?
> 
> tike64 at gmail.com wrote:
> > Mark Jackson wrote:
> >> A sort of 'make install' which would:-
> >>
> >> (a) delete the output/target contents
> >> (b) copy target_skeleton to output/target
> >> (c) run 'make install' on all selected packages (re-compiling if
> >> required)
> >>
> >> I'd find that *most* useful !!
> > 
> > I would also find it useful but, while we are waiting it, 
> this might 
> > be of some value:
> > 
> > rm -rf output/build/.root output/target `find -name 
> *target_installed`
> 
> Seems like a sledgehammer to crack a nut, and it still 
> recompiles uclibc
> *but* it's almost exactly what I was thinking about.
> 
> I'd still like a more formal approach to doing this, and I 
> can't believe that my requirements differ widely from most 
> other developers !?!
> 
> Mark

I'm missing that too.
Every time I add/change/remove a file in my target_skeleton/ i have to
"make distclean;make menuconfig;make" or i have to add it to
project_<arch>/project/root/ too and run make.
I would love to see something like that you have described in buildroot.
I have not enough experience with Makefiles and buildroot to write it,
otherwise i would have done so, that would have saved me hours of
compile time. Especially the toolchain tooks very very long.

Sebastian