FreeLists / openbeos / [openbeos] Headers

["David Reid" <mail@xxxxxxxxxxxxxx>]

How about we do this for the headers?

Rather than have the posix and be trees, we just have one, and it's starting
point is at headers/obos/public

From there we just have the subdirectories we need and fill them as
required. Then when we come to install we just copy the whole damn tree into
the install directory and that's it! Job done. This simplifies the choice of
where to put headers and should simplify the include paths for the build. If
a user may need to use it, it goes into public, if it's only used for
building the os it goes in private.

So we'd end up with something akin to

/
/arch
/arpa/
/add-ons/
/app/
/be_app/
/device/
...
/kernel/
...
/net/
/netinet/
...
/support/
/sys/

While it makes for a big tree, I don't really see the problem with that and
does make the whole thing easier for people. Following Be's example and
having C headers in lower case and C++ in mixed case will make it even more
obvious.

Anyway, just more thoughts.

david