[examples-v2 commit] Add various programs to report default attributes for various POSIX objects

Chris Johns chrisj at rtems.org
Thu Oct 11 02:25:09 UTC 2018

> On 9 Oct 2018, at 2:33 pm, Joel Sherrill <joel at rtems.org> wrote:
>> On Tue, Oct 9, 2018, 4:19 PM Chris Johns <chrisj at rtems.org> wrote:
>> On 8/10/18 8:56 am, Joel Sherrill wrote:
>> > diff --git a/posix_api/Makefile b/posix_api/Makefile
>> > index b070ea9..8af26dc 100644
>> > --- a/posix_api/Makefile
>> > +++ b/posix_api/Makefile
>> > @@ -4,5 +4,14 @@ include $(RTEMS_SHARE)/make/directory.cfg
>> I had forgotten the Makefile.in build support was present in this repo. I have
>> not used Makefile.inc when building any RTEMS exe for decades.
>> Is it a good idea to have both or should we have waf as the method to build the
>> examples? For example you end up with this in the repo ..
>> https://git.rtems.org/examples-v2/tree/misc/wscript#n18
> Both still work. I have been working under the impression that 5.1 was the last release with these supported. When we switch to watch for RTEMS, we can kill these.

Ok that fine. What about a README.Makefil to say this and an example showing how to us it. It help our users in the forest that is RTEMS after building a kernel. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20181010/32ff283a/attachment-0002.html>

More information about the devel mailing list