On Wed, Aug 03, 2022 at 07:56:34AM +0200, Jan Beulich wrote: > On 02.08.2022 19:09, Anthony PERARD wrote: > > On Mon, Jul 11, 2022 at 04:08:55PM +0200, Jan Beulich wrote: > >> Can you confirm things to work when > >> building locally in just this subdir, e.g. via > >> > >> make -sC .../tools/fuzz/x86_instruction_emulator > >> CC=/build/afl/2.52b-base/afl-gcc > >> > >> ? > > > > Yes, that still works. But I'm not sure why you would ask since the > > tools/ build system works this way, execution of make in a subdir > > doesn't depends on the execution from the parent dir (it doesn't > > depends on anything in the envvar). > > Oh, I wasn't even aware of this as a general feature in tools/. Is > this going to survive your rework to use non-recursive makefiles?
Yes. Executing `make` in any subdir will still works. It should be even better than the current situation, even in a fresh clone, we could simply run `./configure && make -C subdir` and make will make everything needed, that is probably the "include/" dir and the "libs/" if they are needed by anything in that subdir. At the moment, one can run ./configure then `make -C tools/include` and `make -C tools/libs` and probably run make in most subdir without having to wait for a long run of `make build-tools`. Cheers, -- Anthony PERARD
