On Thu, Sep 12, 2019 at 2:09 PM Gedare Bloom <ged...@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 + ... --joel > > On Tue, Aug 27, 2019 at 9:48 AM Vaibhav Gupta <vaibhavgupt...@gmail.com> > 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
