Skip to contentSkip to conversation

Missing 'make install' option ?

Buildroot Mark Jackson 4 participants 8 messages Oct 15, 2009 – Oct 16, 2009

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 9 lines · 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* !!

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

#2 lore raw
Quoted 6 lines · Sven Neumann
Quoted 5 lines · 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.

Quoted 8 lines
Quoted 4 lines

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

#3 lore raw
Quoted 7 lines · Mark Jackson

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

#4 lore raw
Quoted 8 lines · tike64 at gmail.com wrote:
Quoted 7 lines · Mark Jackson

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)

Quoted 6 lines
Quoted 1 line

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

#5 lore raw
Quoted 24 lines

Subject: Re: [Buildroot] Missing 'make install' option ?

Quoted 11 lines · tike64 at gmail.com wrote:
Quoted 8 lines · Mark Jackson

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

Quoted 3 lines

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.

Quoted 5 lines

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

#6 lore raw
In reply to Mark Jackson
Quoted 5 lines · Mark Jackson

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

#7 lore raw
Quoted 9 lines · Sven Neumann
Quoted 5 lines · Mark Jackson

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

??