Draft for moving network headers from RTEMS to newlib

[Chris Johns]

On 26/04/2016 01:06, Christian Mauderer wrote:
> currently we try to remove the network specific POSIX headers from
> RTEMS. Instead, we add current headers from FreeBSD to newlib. This will
> simplify the build process of some libraries that depend on the network
> (like LibreSSL).

What does this work flow offer over building and installing an RTEMS 
kernel for a BSP and adding that path to the packages include paths?

How do you get the flags for the compiler to build the package?

How are any tests present in the package built and linked?

Do we risk limited the functionality of a package by restricting the 
headers exposed to only standards based headers? There are headers which 
some packages use that will not be present.

> Further it will be another step into the direction of
> extracting the old RTEMS network stack and build it as an independent
> package.

Is this just a specialised version of the generic vertical integration 
problem being discussed in the civetweb thread?

I am not against standards based headers like the ones being discussed 
here being move to newlib however I currently do not see what the 
advantage is and how value is being adding over a specific build order 
of packages.

I still see all the normal issues of CFLAGS, LDFLAGS, 3rd party package 
dependence still being present once this work is completed.

Chris