Split up confdefs.h into multiple header files?

[Joel Sherrill]

On Thu, Dec 5, 2019 at 7:56 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> Hello,
>
> the next thing I would like to work on is a specification of the
> application configuration (e.g. confdefs.h defines).
>
> The confdefs.h header file is quite big and difficult to review. What do
> you think about splitting this file into smaller parts, so that
> confdefs.h consists of something like this:
>
> #include <rtems/config/classictask.h>
> #include <rtems/config/classicsema.h>
> #include <rtems/config/bdbuf.h>
> #include <rtems/config/posixthread.h>
> ...
>
> ?
>

I think this MIGHT be a good idea. But I think you might want to
look at the top and bottom of the file first. What files will instantiate
the
data structures? There is also some error checking at the bottom
which probably could be a sub-file.

Will there be logic to prevent including them from any other file?

What about file system configuration?

Once you decompose that, will there actually be enough content to
justify a file per manager/capability? I understand this makes it easier
to track to a manager.

Where do user init task/threads go?

Just random thoughts? I can see "capability" or "area" oriented files
but going down to a manager feels too fine grain.

--joel




>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20191205/288fe5d7/attachment.html>