[PATCH] Don't hardcode target dependencies

M.Canales.es macana at macana-es.com
Thu Mar 15 14:17:48 PDT 2007


El Jueves, 15 de Marzo de 2007 21:40, George Boudreau escribió:

>    When I make the drastic changes to the makefile format the goal was
> size reduction and maintaining the book build style. If I wanted to
> build a particular package multiple times I forced a 'build failure' and
> the makefile would abort. Not a practical work method for the general
> public.

Plus, you must be watching the build to can stop it on the required point.


>    If you want to abort the makefile after a selected package has been
> built we would need a testing method for a breakpoint variable passed on
> the cmd line.
>   make BREAKPOINT=028-binutils-pass1

That looks feasible and simple to implement. Very good idea :-)

>    If the breakpoint is tested _before_ the housekeeping the dependency
> flag/file is not created and the package can be rebuilt without
> intervention.

I think that could be better to stop after the touch to allow target-by-target 
builds. To redo an already done one is as simple as rm it touched file.

>    However, if you are looking for even more flexibility we could
> beg/borrow/recycle some code from the LiveCD makefile. They have
> implemented a few 'make [package-only]' routines and the same could be
> done for jhalfs.

What more flexibility could be needed beyond to can stop at a dessired point 
or to can run the targets one-by-one?


-- 
Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfromscratch.org
LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info
TLDP-ES:                           http://es.tldp.org



More information about the alfs-discuss mailing list