On Fri, 15 Mar, 2019, 12:27 AM Joel Sherrill <j...@rtems.org wrote: > It's always good to discuss old project ideas and make sure they are still > sane and useful. > Yes I agree, I meant for GSoC I am focusing on "POSIX Compilance" But any project ideas, old/new, always trigger my curiosity, the reason I asked it in the query, we can work on it.
> > On the POSIX Compliance, I am make sure it is said publicly that methods > included in > FACE Technical Standard profiles that are missing are the highest priority > to add. And > this is documented in the Compliance document. > Yah it was clear. I am following the steps you said. -Have got FACE Technical Standard pdf. -I found that aio.h has got its palce in newlib. -Still exploring and analysing. > > On Thu, Mar 14, 2019 at 12:34 AM Vaibhav Gupta <vaibhavgupt...@gmail.com> > wrote: > >> After having off-list discussion with Dr Joel, I have already got a >> direction in project "POSIX Compilance" and I am giving my all time, >> solely, on that only. >> . >> But I am thankful to community that they gave their attention on this >> query, of mine. >> >> On Tue, Mar 12, 2019 at 3:56 PM Vaibhav Gupta <vaibhavgupt...@gmail.com> >> wrote: >> >>> >>> On Mon, Mar 11, 2019 at 3:24 AM Joel Sherrill <j...@rtems.org> wrote: >>> >>>> >>>> >>>> On Sun, Mar 10, 2019, 3:57 PM Chris Johns <chr...@rtems.org> wrote: >>>> >>>>> On 11/3/19 9:06 am, Joel Sherrill wrote: >>>>> > On Sun, Mar 10, 2019, 2:29 PM Chris Johns <chr...@rtems.org >>>>> > <mailto:chr...@rtems.org>> wrote: >>>>> > >>>>> > On 6/3/19 10:23 pm, Amaan Cheval wrote: >>>>> > > I'm not sure if the project is open, but if it is, I'd be >>>>> willing to >>>>> > co-mentor. >>>>> > >>>>> > Thanks. >>>>> > >>>>> > > >>>>> > > On Wed, Mar 6, 2019, 2:45 PM Vaibhav Gupta < >>>>> vaibhavgupt...@gmail.com >>>>> > <mailto:vaibhavgupt...@gmail.com> >>>>> > > <mailto:vaibhavgupt...@gmail.com <mailto: >>>>> vaibhavgupt...@gmail.com>>> wrote: >>>>> > > >>>>> > > I was exploring for more open projects and found the >>>>> following one. >>>>> > > >>>>> > > - Port V8 Javascript Engine : >>>>> > > https://devel.rtems.org/wiki/Developer/Projects/Open/V8 >>>>> > > >>>>> > > Not much information is given about it and even the above >>>>> link was >>>>> > modified >>>>> > > in 2015. I want to know if the project is open for GSOC >>>>> 2019? >>>>> > > If it is open, then It would be great to know if someone >>>>> would like to >>>>> > > mentor it. I would like to discuss further on it. >>>>> > >>>>> > I suggest you create a ticket for this project like the other >>>>> GSoC tickets we >>>>> > have and add some additional details .. >>>>> > >>>>> > - Please list the archs supported, this is viewable in the src >>>>> tree. >>>>> > - Add something about needing Chromium's depot_tools. I see >>>>> FreeBSD is not >>>>> > listed but chromium is available on FreeBSD. >>>>> > - Investigate the build system and if it is possible to >>>>> cross-compile. >>>>> > >>>>> > I'm a bit concerned that it may require things RTEMS does not have. >>>>> >>>>> If it cannot be cross-compiled it would be hard to maintain long term. >>>>> >>>>> > Does it mmap in ways we don't support? >>>>> >>>>> I also wondered. There is an abstraction in the POSIX platform code >>>>> for mmap so >>>>> a grep would let us know. >>>>> >>>>> > I doubt it forks new processes but that has to be answered. >>>>> >>>>> Yeap. >>>>> >>>>> > Some basic research plus an attempt to compile it for RTEMS with >>>>> > problem sections disabled is a good first step of any porting >>>>> evaluation. >>>>> >>>>> Yes. >>>>> >>>>> > FWIW I looked at porting the PDF viewer from chromium to RTEMS. >>>>> Their build >>>>> > system seemed quite complex. >>>>> >>>>> Firefox uses a js project held in github ( >>>>> https://github.com/mozilla/pdf.js/). >>>>> >>>> >>>> +1 >>>> >>>> Just to be clear, I am not discouraging this as a project. I just think >>>> it needs some homework to.make sure it is feasible. >>>> >>> I will check the things. >>> >>>> >>>>> Chris >>>>> >>>>
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
