Re: Add chapter for newib build in RTEMS Docs
On Fri, Nov 1, 2019 at 11:14 PM Gedare Bloom wrote: > On Thu, Oct 31, 2019 at 5:14 AM Joel Sherrill wrote: > > > > > > > > On Thu, Oct 31, 2019, 1:30 AM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> > >> On 30/10/2019 10:35, Vaibhav Gupta wrote: > >> > 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? > >> > >> I think nobody was in favour of adding a new document. I would place it > >> in the RTEMS Software Engineering guide. I think we need a chapter for > >> tool and 3rd party software maintenance topics. > > > > > > Yes. > > > > And another section on tool selection requirements. But this is beyond > this patch. > +1 > > Mainly, the content just needs to be written, then we can integrate it. > Sure then, I will proceed with it. > > >> > >> > >> -- > >> 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.hu...@embedded-brains.de > >> PGP : Public key available on request. > >> > >> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. > >> ___ > >> devel mailing list > >> devel@rtems.org > >> http://lists.rtems.org/mailman/listinfo/devel > > > > ___ > > devel mailing list > > devel@rtems.org > > http://lists.rtems.org/mailman/listinfo/devel > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Add chapter for newib build in RTEMS Docs
On Thu, Oct 31, 2019 at 5:14 AM Joel Sherrill wrote: > > > > On Thu, Oct 31, 2019, 1:30 AM Sebastian Huber > wrote: >> >> On 30/10/2019 10:35, Vaibhav Gupta wrote: >> > 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? >> >> I think nobody was in favour of adding a new document. I would place it >> in the RTEMS Software Engineering guide. I think we need a chapter for >> tool and 3rd party software maintenance topics. > > > Yes. > > And another section on tool selection requirements. But this is beyond this > patch. +1 Mainly, the content just needs to be written, then we can integrate it. >> >> >> -- >> 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.hu...@embedded-brains.de >> PGP : Public key available on request. >> >> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. >> ___ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel > > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Add chapter for newib build in RTEMS Docs
On Thu, Oct 31, 2019, 1:30 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 30/10/2019 10:35, Vaibhav Gupta wrote: > > 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? > > I think nobody was in favour of adding a new document. I would place it > in the RTEMS Software Engineering guide. I think we need a chapter for > tool and 3rd party software maintenance topics. > Yes. And another section on tool selection requirements. But this is beyond this patch. > > -- > 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.hu...@embedded-brains.de > PGP : Public key available on request. > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Add chapter for newib build in RTEMS Docs
On 30/10/2019 10:35, Vaibhav Gupta wrote: 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? I think nobody was in favour of adding a new document. I would place it in the RTEMS Software Engineering guide. I think we need a chapter for tool and 3rd party software maintenance topics. -- 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.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Add chapter for newib build in RTEMS Docs
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 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.hu...@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 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.hu...@embedded-brains.de >> PGP : Public key available on request. >> >> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. >> ___ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel > > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Add chapter for newib build in RTEMS Docs
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.hu...@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 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.hu...@embedded-brains.de > PGP : Public key available on request. > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Add chapter for newib build in RTEMS Docs
On Fri, Sep 13, 2019 at 4:12 AM Joel Sherrill wrote: > On Thu, Sep 12, 2019 at 2:09 PM Gedare Bloom 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. > Standalone guide sounds good because I am also confused which manual will be the ideal fit. > > 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 > + ... > > Yes, for now I have not much content as other docs are having. But the content I proposed are important ones. It will save enough time of future developers. And I am sure that content will be generated with development of newlib, other third party libraries, and RTEMS. - Vaibhav > --joel > > > > > On Tue, Aug 27, 2019 at 9:48 AM Vaibhav Gupta > wrote: > > > > > > Hello, > > > As RTEMS is using "Newlib" as its C library, sometimes RTEMS > > > developers need to contribute codes directly to it. For example in > > > my GSoC Project, I have to port various headers to Newlib. > > > > > > This requires building Newlib on local system, making changes, > > > using right autoconf-tools version, creating patches, etc. > > > > > > In my case I referred to the blogs of Aditya. Hesham gave me few advice > > > during weekly meeting. > > > > > > I was hoping if we can provide a separate chapter for this in RTEMS > Docs User Manual. > > > It will be helpful for new developers and also new GSoC and GCI > students. > > > > > > Is it okay to proceed with ? > > > > > > Vaibhav Gupta > > > ___ > > > devel mailing list > > > devel@rtems.org > > > http://lists.rtems.org/mailman/listinfo/devel > > ___ > > devel mailing list > > devel@rtems.org > > http://lists.rtems.org/mailman/listinfo/devel > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Add chapter for newib build in RTEMS Docs
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 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.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Add chapter for newib build in RTEMS Docs
On 13/9/19 8:42 am, Joel Sherrill wrote: > On Thu, Sep 12, 2019 at 2:09 PM Gedare Bloom 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? Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Add chapter for newib build in RTEMS Docs
On Thu, Sep 12, 2019 at 2:09 PM Gedare Bloom 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 + ... --joel > > On Tue, Aug 27, 2019 at 9:48 AM Vaibhav Gupta > wrote: > > > > Hello, > > As RTEMS is using "Newlib" as its C library, sometimes RTEMS > > developers need to contribute codes directly to it. For example in > > my GSoC Project, I have to port various headers to Newlib. > > > > This requires building Newlib on local system, making changes, > > using right autoconf-tools version, creating patches, etc. > > > > In my case I referred to the blogs of Aditya. Hesham gave me few advice > > during weekly meeting. > > > > I was hoping if we can provide a separate chapter for this in RTEMS Docs > > User Manual. > > It will be helpful for new developers and also new GSoC and GCI students. > > > > Is it okay to proceed with ? > > > > Vaibhav Gupta > > ___ > > devel mailing list > > devel@rtems.org > > http://lists.rtems.org/mailman/listinfo/devel > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Add chapter for newib build in RTEMS Docs
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. On Tue, Aug 27, 2019 at 9:48 AM Vaibhav Gupta wrote: > > Hello, > As RTEMS is using "Newlib" as its C library, sometimes RTEMS > developers need to contribute codes directly to it. For example in > my GSoC Project, I have to port various headers to Newlib. > > This requires building Newlib on local system, making changes, > using right autoconf-tools version, creating patches, etc. > > In my case I referred to the blogs of Aditya. Hesham gave me few advice > during weekly meeting. > > I was hoping if we can provide a separate chapter for this in RTEMS Docs User > Manual. > It will be helpful for new developers and also new GSoC and GCI students. > > Is it okay to proceed with ? > > Vaibhav Gupta > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
