Add chapter for newib build in RTEMS Docs

Vaibhav Gupta vaibhavgupta40 at gmail.com
Wed Oct 30 09:35:19 UTC 2019


So what's the final stand on this?

Should be working on standalone guide or add the contents to RTEMS Software
Engineering guide as suggested by Sebastian?

--Vaibhav


On Fri, Sep 13, 2019, 5:40 PM Vaibhav Gupta <vaibhavgupta40 at gmail.com>
wrote:

> Well I have no problem in working on standalone guide or adding it to
> Software Engineering Manual. I saw that most of the development related
> work,
> even about patches, were in User Manual, so I proposed it at first place.
>
> - Vaibhav
>
> On Fri, Sep 13, 2019 at 10:40 AM Sebastian Huber <
> sebastian.huber at embedded-brains.de> wrote:
>
>> On 13/09/2019 03:34, Chris Johns wrote:
>> > On 13/9/19 8:42 am, Joel Sherrill wrote:
>> >> On Thu, Sep 12, 2019 at 2:09 PM Gedare Bloom<gedare at rtems.org>  wrote:
>> >>> Hello Vaibhav,
>> >>>
>> >>> It would be nice to provide such documentation, but I don't know that
>> >>> we have an existing location that would be an ideal fit. I think the
>> >>> topic is out of scope for User Manual. If you are motivated to write
>> >>> something though, you could prepare it first as a standalone guide.
>> >> If we have a name for the document like "Maintainers Guide" or
>> something,
>> >> it could have a focus on procedures that only core developers would
>> need.
>> >>
>> >> + bootstrapping newlib and building it independently
>> >> + modifying gcc, running tests,
>> >> + submitting Coverity runs
>> >> + running Doxygen
>> >> + ...
>> > These are all valid and important however can these reside in the
>> Software
>> > Engineering manual?
>> >
>> > We current have ...
>> >
>> >   1. RTEMS Software Engineering
>> >   2. RTEMS Filesystem Design Guide
>> >   3. RTEMS Development Environment Guide
>> >   4. RTEMS BSP and Driver Guide
>> >
>> > plus 'RTEMS BSP and Driver Guide' which I am not sure about. All these
>> cover
>> > some aspect of maintaining and developing RTEMS. Should we be
>> considering
>> > consolidation rather than expansion?
>>
>> Yes, we should definitely aim to consolidate the documentation set and
>> not add new documents. I would put this topic into the RTEMS Software
>> Engineering.
>>
>> --
>> 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.
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20191030/dfd14432/attachment-0001.html>


More information about the devel mailing list