porting aio.h to newlib

Eshan Dhawan eshandhawan51 at gmail.com
Tue Apr 21 17:07:33 UTC 2020


On Tue, Apr 21, 2020 at 4:32 AM Joel Sherrill <joel at rtems.org> wrote:

>
>
> On Mon, Apr 20, 2020 at 5:11 PM Eshan Dhawan <eshandhawan51 at gmail.com>
> wrote:
>
>> hello everyone,
>>
>> RTEMS has the implementation of aio.h.
>> But for simplicity it needs to be shifted to newlib.
>> where would be the header file added and
>> where would be the source code files added??
>> Also what would be the other changes that would be required to setup the
>> methods ??
>>
>
> You wouldn't be porting the aio implementation to newlib, just moving the
> .h file.
>
> The implementation is very RTEMS specific and there is no reason to move
> it since it can't be shared.
>
> If our aio.h is portable enough to apply to other environments, then it
> can go in the main include directory of newlib.
>
> If not, then it goes under an RTEMS specific directory.
>
> Do you think it is portable or RTEMS specific in its contents?
>
It seems to be portable and not RTEMS specific. So it can be added to the
main include folder.

>
> And before it is moved, we may want to make a sweep to update the D7 page
> numbers. That is like a 1993 paper draft of POSIX. :)
>
Could you elaborate this part, please?

thanks :)
-Eshan

> --joel
>
>
>>
>> Thanks:)
>> -Eshan
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200421/b643b5ce/attachment.html>


More information about the devel mailing list