<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 22, 2021 at 11:55 AM Gedare Bloom <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, Mar 22, 2021 at 10:50 AM Joel Sherrill <<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a>> wrote:<br>
><br>
><br>
><br>
> On Mon, Mar 22, 2021 at 11:30 AM Gedare Bloom <<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>> wrote:<br>
>><br>
>> On Sat, Mar 20, 2021 at 12:33 PM Eshan Dhawan <<a href="mailto:eshandhawan51@gmail.com" target="_blank">eshandhawan51@gmail.com</a>> wrote:<br>
>> ><br>
>> > Hello Everyone,<br>
>> > I wanted to take Packaging Micro Python up as GSOC project this summer and the project will also include packaging LUA and picoC<br>
>> > The ticket for Micro Python : <a href="https://devel.rtems.org/ticket/4349" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/4349</a><br>
>> > What would be the complete Scope of the project?<br>
>> > And what would be a good starting point?<br>
>> ><br>
>><br>
>> Well, I guess Joel must have described the task, so I'll leave it to<br>
>> him to fill in some more details.<br>
>><br>
>> Adding RSB packages may be not sufficient coding work for GSoC. It is<br>
>> important in the proposal to identify what would be the coding<br>
>> activities involved in this project. For example, we know from<br>
>> experience that Lua can just be built from some minor tailoring of its<br>
>> Makefile, so the package is very straightforward. However, the<br>
>> projects you mention are scripting environments, so maybe creating a<br>
>> framework in RTEMS for a "shell/intepreter" that can be built as an<br>
>> add-on by RSB would be a proper way to scope this effort.<br>
><br>
><br>
> I agree that Lua and Micropython should build easy but I had more<br>
> in mind.<br>
><br>
> The full project was language stacks for RTEMS with a better user<br>
> experience for Micropython, Lua, Tcl, etc although I am not sure what<br>
> etc would entail. I am not sure all three can be completed in the new<br>
> GSoC timeframe. All would follow the same pattern:<br>
><br>
> + RSB package offering a reasonable default and access to configuration<br>
> + Examples including at least bare embedded, use of custom commands,<br>
> and integrating with RTEMS shell commands Perhaps interactive use with<br>
> command line history and editing integrated if we have that as a library now.<br>
> + Documentation specific to RTEMS and the examples<br>
><br>
> I imagined completely parallel kits for each embedded language we wanted<br>
> to support.<br>
><br>
> Does that help? Should he plan on Micropython and Lua?<br>
><br>
<br>
Sure. Lua should be easy way to get started and develop the<br>
framework/infrastructure side in Phase 1. Phase 2 could be extension<br>
to micropython / other scripting languages.<br></blockquote><div><br></div><div>OK. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I'm not sure about the RSB design of things, and whether they should<br>
be parallel or capable of integration. Would anyone want to use<br>
multiple interpreters in the same application? If so, they should<br>
build together to avoid conflicts. If not, parallel is fine.<br></blockquote><div><br></div><div>I don't see any reason on our side why that shouldn't work but we </div><div>can't guarantee they don't have symbol conflicts. And I'm not sure</div><div>it would make much sense to integrate both at the same time.</div><div><br></div><div>I'd think you could install both but we'd focus on only using one</div><div>at a time.</div><div><br></div><div>--joel </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> --joel<br>
><br>
>><br>
>> > Thanks<br>
>> > - Eshan<br>
>> > _______________________________________________<br>
>> > devel mailing list<br>
>> > <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
>> > <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
>> _______________________________________________<br>
>> devel mailing list<br>
>> <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
>> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
</blockquote></div></div>