office-gobmx/tail_build
Norbert Thiebaud 1b61693a15 Enough with that...
peter's gbuildifications caused and ocean of red, that
1/ was not followed up by any attempt by the author to fix
2/ I wasted a good part of the weekend to de-entangle with
only partial sucess

reverting the whole mess for now...
to be resubmited when a bit less borked...

This reverts commit c4c160a451.
This reverts commit faef2e51d0.
This reverts commit 057ce1fe29.
This reverts commit a7d34af344.
This reverts commit befae0ceb8.
This reverts commit 433b43bcd2.
This reverts commit 93e2c4a9d2.
2012-11-04 16:33:21 -06:00
..
prj Enough with that... 2012-11-04 16:33:21 -06:00
Makefile
README

This module exist only to take advantage of the ability of gbuild to build
multiple modules in one single Makefile.

A few module that normally get built at the end of the build process
are already converted. this 'pseudo-module' build them all as one.

As module get converted to gbuild they can be added to this module
if they fix the necessary pre-requisite. that is:

To qualify a module must not be the dependant of any other module,
except postprocess or if the other module itself is under tail_build

To migrate a module <foo> under tail_build, one should:
* merge the dependencies declared in <foo>/prj/build.lst into tail_build/prj/build.lst
* remove the module <foo> from postprocess/prj/build.lst dependencies
* remove the module <foo> from tail_build/prj/build.lst dependencies
* add the module name in Module_tail_build.mk in the root of the tree.

This module of course, takes a lot of thought, and dependency work /
statting until it has finished it's business, knows exactly what to
re-build, and can start building just that.