Re: [PATCH 0/3] Improve Makefile robustness and explicitness

[Sebastian Andrzej Siewior <bigeasy@linutronix.de>]

On 2025-11-11 11:29:17 [-0500], Derek Barbosa wrote:
> > The default set should not be something that is not required
> > and is not always provided by the compiler specified as minimum.
> 
> With this tidbit in mind, what else do you propose we strip out and leave to the
> packagers? Is it worth retaining some of the debug & hardening flags, and
> leaving the rest to them?

I don't know what this is part of, I just seen the Makefile bits. I
don't worry if you keep some debug flags and or hardening which are
universal. Just don't set anything special which you might need to
filter out later… Or add later on additional bits once "new" debug or
hardening switches become a thing because this is IMHO not the place for
it. It should be passed by the upper layer.

A simple example would be using cmake: Set the .c files you want to
compile, set the libs you need as dependency and are done. cmake has a
profile for debug, release and release+debug. The build environment can
set custom flags. This is what I see is mostly done.

> Cheers,

Sebastian