> Well it's not really that persuasive. Most people simply let the build > run to completion, but if you have a problem with a job control 3h > timelimit, then create a job that kills itself at 2:59 and then > resubmits itself. That will produce a complete build in 3h chunks > without any need to call sub Makefiles. > Humm, I probably should have explained better how GitlabCI works. It works creating a docker container that have a limited lifespan of 3h max. After that the time is over, this container ceases to exist, leaving no build objects, only the console log. So there is no way of 'resuming' the building from where it stopped. I used the 'job' term because it's how they call it, and I understand it's easily confused with bash jobs. > All of our Makefiles are coded assuming the upper level can prevent > descent into the lower ones. You're proposing to change that > assumption, requiring a fairly large patch set, which doesn't really > seem to provide a huge benefit. > > James I understand your viewpoint. But what I propose is not to change that assumption, but instead give some Makefiles the aditional ability to be called directly and still not build stuff if they were not enabled in .config. But, why these chosen Makefiles, and not all of them? Granularity. What I am trying to achieve with this patchset is the ability of building smaller sets of drivers without accidentally building what is not enabled on .config. And, in my viewpoint, building a single drivers/DRIVERNAME is small enough to be fast in most situations. This change is not supposed to bother the usual way of building the kernel, and it is not even supposed to add overhead to kernel compilation. And it would, at least, solve my problem with the 3h limit, and enable the tool I am building on GiltabCI to help other developers. Thanks for reading, Leonardo Bras
