[PATCH] c-user: Update POSIX API configuration

[Sebastian Huber]

On 31/10/2018 07:41, Chris Johns wrote:
> On 31/10/2018 17:02, Sebastian Huber wrote:
>> On 31/10/2018 02:16, Chris Johns wrote:
>>> On 30/10/2018 18:09, Sebastian Huber wrote:
>>>> Close ##2514.
>>>> ---
>>>>    c-user/configuring_a_system.rst | 34 +++++++++++++++++++++++-----------
>>>>    1 file changed, 23 insertions(+), 11 deletions(-)
>>>>
>>>> diff --git a/c-user/configuring_a_system.rst b/c-user/configuring_a_system.rst
>>>> index eab91ff..78344df 100644
>>>> --- a/c-user/configuring_a_system.rst
>>>> +++ b/c-user/configuring_a_system.rst
>>>> @@ -517,7 +517,7 @@ NOTES:
>>>>        ``CONFIGURE_EXTRA_TASK_STACKS``.
>>>>          The maximum number of POSIX threads is specified by
>>>> -    ``CONFIGURE_MAXIMUM_POSIX_THREADS``.
>>>> +    :ref:`CONFIGURE_MAXIMUM_POSIX_THREADS <CONFIGURE_MAXIMUM_POSIX_THREADS>`.
>>>>          A future enhancement to ``<rtems/confdefs.h>`` could be to eliminate the
>>>>        assumption that all tasks have floating point enabled. This would require
>>>> @@ -1051,9 +1051,11 @@ NOTES:
>>>>    POSIX API Configuration
>>>>    =======================
>>>>    -The parameters in this section are used to configure resources for the RTEMS
>>>> -POSIX API.  They are only relevant if the POSIX API is enabled at configure
>>>> -time using the ``--enable-posix`` option.
>>>> +The parameters in this section are used to configure resources for the POSIX
>>>> +API supported by RTEMS.  Most POSIX API objects are available by default since
>>>> +RTEMS 5.1.  The queued signals and timers are only available if the optional
>>>> +parts of the POSIX API are enabled at BSP configure time using the
>>> BSP configure time? Is this in common use? The User manual says ...
>>>
>>> https://docs.rtems.org/branches/master/user/installation/kernel.html#building-a-bsp
>>>
>>>
>>> ... we "configure RTEMS" for a BSP.
>> In the "Configuring a System" chapter the term "configure RTEMS" could be
>> confusing.
> Yes, this is true. We should settle on something standard and use it consistently.

Yes, I think we need some standard terms for the various configurations.

>
>> What about:
>>
>> The queued signals and timers are only available if RTEMS has been
>> built with the ``--enable-posix`` build configuration option.
>>
> "build configuration option" or "build configure option"?
>
> I like 'build configuration'.

I think the "build configuration" is the set of all "build configuration 
options" and --enable-posix is one of these options.

I would avoid the name "configure". Maybe we have some time in the 
future a "waf config --enable-posix".

> Does this mean 'configuration' is the run-time
> configuration or should this be explicit as well?

This is a link-time configuration. I think "application configuration" 
is used in some places for it, although the application is not 
configured. What is configured is the RTEMS executive.

-- 
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.