RFC: cpukit/libcompat Was Re: [rtems commit] PR1908: QoS library for CBS scheduler
joel.sherrill at OARcorp.com
Thu Apr 19 19:14:52 UTC 2012
On 04/19/2012 01:30 PM, Gedare Bloom wrote:
> My question was buried by other inanities.
> qreslib implements a fairly thin compatibility layer for part of a
> Linux API of AQuoSA, so I don't think the rtems/ subdirectory is the
> right place (not an RTEMS API). How does a libcompat subdirectory of
> cpukit sound? I propose we add a libcompat which can include a
> subdirectory itself for arbitrary API compatibility layers. For the qres
> work it would be cpukit/libcompat/qres/ and probably just have the
> qreslib.h file.
I don't see the problem with it being a top level library
in cpukit. If you start done this path, then you have to
ask yourself what makes something top level versus
"compat" with something. Would we move more code
down under libcompat?
Do we install a .h file with the proper name and
contents so applications would have source compatibility?
I am prone to leave it at the cpukit level. I would have
complained when the code was put in the PR last summer
if I didn't like that of it.
> rtems-devel mailing list
> rtems-devel at rtems.org
Joel Sherrill, Ph.D. Director of Research& Development
joel.sherrill at OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
More information about the devel