[RFC] Add namespacing to configs and includes to fix conflicts

[Krishna Chaitanya]

On Mon, Sep 15, 2025 at 3:00 PM Johannes Berg <johannes at sipsolutions.net> wrote:
>
> On Mon, 2025-09-15 at 14:53 +0530, Krishna Chaitanya wrote:
> > >
> > > I'm thinking ... why is this even an issue? Can you really not fix your
> > > include paths/command lines in Zephyr?
> >
> > We already have a few workarounds in Zephyr to address this. But isn't this
> > a proper solution to fix the root cause (helps any other such projects)?
>
> I guess I don't understand what you think the root cause is?

>From the Linux PoV, no issue here, but for other forks like Zephyr,
having to workaround
conflicts, e.g., wpa_supplicant is built as a library and "common.h"
is conflicting with
another library, we can solve this within the Zephyr, but having
hostap use a separate
namespace would be helpful.

> > IMHO, it also helps readability, esp. the header file paths giving some context,
> > instead of just the filename.
>
> That seems like an odd thing to say - in the hostap project clearly the
> context is ... the hostap project?

Not just the top-level directory, but also context internal to hostap, e.g.,
#include "common.h" -> #include <src/utils/common.h> (for internal) and
#include <hostap/src/utils/common.h> (for external projects). Keeping aside
the external project, the internal context is also helpful IMHO.