Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.lang.c++ Subject: Re: Adding compilation arguments to 4000 make files. . . Date: Sat, 10 Aug 2019 09:43:17 +1200 Lines: 35 Message-ID: References: <08%2F.113866$qC7.92294@fx11.iad> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net hcGKz/W+UvFROIQ0ZbQbUggQ9Gw3Q91SSzaf5HgtpnsuVxmgDZ Cancel-Lock: sha1:VmdCrJ6sQJP77xRP4chHmMOGNQ0= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 In-Reply-To: Content-Language: en-US Xref: csiph.com comp.lang.c++:67506 On 10/08/2019 02:36, Scott Lurndal wrote: > Jorgen Grahn writes: >> On Thu, 2019-08-08, Scott Lurndal wrote: >>> Jorgen Grahn writes: >>>> On Thu, 2019-08-08, Frederick Gotham wrote: >>>>> >>>>> I'm working on a firmware project at the moment, it's running on >>>>> embedded Linux for a 64-Bit ARM processor (aarch64). >>>>> >>>>> There's the main Makefile, which uses "make -C" to invoke further >>>>> Makefiles in nested subdirectories. Altogether there's four thousand >>>>> Makefiles. >>>> >>>> Someone somewhere should be fired ... >>> >>> Why? Doesn't seem completely out-of-line: >>> >>> $ find bootloader firmware -name Makefile | wc -l >>> 929 >> >> Because I believe in the Recursive Make Considered Harmful paper: >> http://aegis.sourceforge.net/auug97.pdf > > That paper has never been convincing to me, nor anyone that I've > ever worked with, nor any unix or linux os or other large sourcebase > that I've worked on professionally. It convinced me long ago... Recursive Make makes distributed building much harder. My current project code base is modest (about 3,000 source files in multiple libraries) but we only have one "makefile". It isn't actually a makefile, we use premake to to generate a ninja build file. -- Ian.