how to port things from spresense sdk

[Takashi Yamamoto <ya...@midokura.com.INVALID>]

hi,

I wanted to use mqtt on nuttx.
I found a nuttx port of paho.mqtt.embedded-c in spresense sdk. [1]
I modified it for my nuttx $(APPDIR)/external.
you can find it here: https://github.com/yamt/mqtt_nuttx
while it worked, i'm not quite happy with having a fork like this.
can anyone suggest a better way? thank you.

[1] https://github.com/sonydevworld/spresense/tree/master/externals/mqtt

Re: how to port things from spresense sdk

[Alin Jerpelea <je...@gmail.com>]

my colleague worked on it
https://developer.sony.com/posts/zerynth-provides-python-support-for-spresense-microcontroller-board-from-sony/


Regards
Alin


On Mon, Feb 10, 2020 at 5:16 PM Xiang Xiao <xi...@gmail.com>
wrote:

> Alin,
> do you upstream your work? I can't find here:
> https://github.com/micropython/micropython/tree/master/ports
> There even has a zephyr porting.
> It's greet if you can upstream nuttx porting to the mainline.
>
> On Tue, Feb 11, 2020 at 12:04 AM Alin Jerpelea <je...@gmail.com> wrote:
> >
> > Hi
> >
> > as a best practice instead of forking a project and maintaining it you
> > should try to upstream the needed patches do that the project can be
> built
> > on top of NuttX.
> >
> > For reference you can check how microPython or circuit python are built
> on
> > top of NuttX without the need of forking the code
> >
> https://www.adafruitdaily.com/2019/10/29/circuitpython-snakes-its-way-to-the-sony-spresense-sparkfun-qwiic-micro-and-arduino-nano-33-ble-sense-python-adafruit-circuitpython-pythonhardware-circuitpython-micropython-thepsf-adafruit/
> >
> > This way each project shares the maintenance on the parts that belong to
> it
> >
> > Regards
> > Alin
> >
> >
> > On Mon, Feb 10, 2020 at 4:53 PM Gregory Nutt <sp...@gmail.com>
> wrote:
> >
> > >
> > > >>> How about we host the active project porting on github.com/nuttx?
> so
> > > >>> the community could share the work.
> > > >> The ideal solution would be to have the Pahu MQTT support NuttX
> natively
> > > >> in their code.  Then you do not have to port it at all.  We don't
> want
> > > >> responsibility for maintaining forks of other people's code.  It is
> a
> > > >> large effort that takes a lifetime commitment.  We have never done a
> > > >> good job trying that in the past.
> > > > i agree it's ideal.
> > > > is there a "canonical" way for a software to have native nuttx
> support?
> > > > like having the top-level "debian" directory for debian packaging
> stuff.
> > >
> > > You should talk to Alan Carvalho de Assis.  It has been his dream for a
> > > long time to get a NuttX package building system (like the original
> > > Buildroot or OpenEmbedded) for NuttX.  The apps/ directory build
> > > framework might be a starting point but I don't think anyone has done
> > > anything like that other than just talk about what a good idea it is.
> > >
> > >
> > >
> > >
>

Re: how to port things from spresense sdk

[Xiang Xiao <xi...@gmail.com>]

Alin,
do you upstream your work? I can't find here:
https://github.com/micropython/micropython/tree/master/ports
There even has a zephyr porting.
It's greet if you can upstream nuttx porting to the mainline.

On Tue, Feb 11, 2020 at 12:04 AM Alin Jerpelea <je...@gmail.com> wrote:
>
> Hi
>
> as a best practice instead of forking a project and maintaining it you
> should try to upstream the needed patches do that the project can be built
> on top of NuttX.
>
> For reference you can check how microPython or circuit python are built on
> top of NuttX without the need of forking the code
> https://www.adafruitdaily.com/2019/10/29/circuitpython-snakes-its-way-to-the-sony-spresense-sparkfun-qwiic-micro-and-arduino-nano-33-ble-sense-python-adafruit-circuitpython-pythonhardware-circuitpython-micropython-thepsf-adafruit/
>
> This way each project shares the maintenance on the parts that belong to it
>
> Regards
> Alin
>
>
> On Mon, Feb 10, 2020 at 4:53 PM Gregory Nutt <sp...@gmail.com> wrote:
>
> >
> > >>> How about we host the active project porting on github.com/nuttx? so
> > >>> the community could share the work.
> > >> The ideal solution would be to have the Pahu MQTT support NuttX natively
> > >> in their code.  Then you do not have to port it at all.  We don't want
> > >> responsibility for maintaining forks of other people's code.  It is a
> > >> large effort that takes a lifetime commitment.  We have never done a
> > >> good job trying that in the past.
> > > i agree it's ideal.
> > > is there a "canonical" way for a software to have native nuttx support?
> > > like having the top-level "debian" directory for debian packaging stuff.
> >
> > You should talk to Alan Carvalho de Assis.  It has been his dream for a
> > long time to get a NuttX package building system (like the original
> > Buildroot or OpenEmbedded) for NuttX.  The apps/ directory build
> > framework might be a starting point but I don't think anyone has done
> > anything like that other than just talk about what a good idea it is.
> >
> >
> >
> >

Re: how to port things from spresense sdk

[Alin Jerpelea <je...@gmail.com>]

Hi

as a best practice instead of forking a project and maintaining it you
should try to upstream the needed patches do that the project can be built
on top of NuttX.

For reference you can check how microPython or circuit python are built on
top of NuttX without the need of forking the code
https://www.adafruitdaily.com/2019/10/29/circuitpython-snakes-its-way-to-the-sony-spresense-sparkfun-qwiic-micro-and-arduino-nano-33-ble-sense-python-adafruit-circuitpython-pythonhardware-circuitpython-micropython-thepsf-adafruit/

This way each project shares the maintenance on the parts that belong to it

Regards
Alin


On Mon, Feb 10, 2020 at 4:53 PM Gregory Nutt <sp...@gmail.com> wrote:

>
> >>> How about we host the active project porting on github.com/nuttx? so
> >>> the community could share the work.
> >> The ideal solution would be to have the Pahu MQTT support NuttX natively
> >> in their code.  Then you do not have to port it at all.  We don't want
> >> responsibility for maintaining forks of other people's code.  It is a
> >> large effort that takes a lifetime commitment.  We have never done a
> >> good job trying that in the past.
> > i agree it's ideal.
> > is there a "canonical" way for a software to have native nuttx support?
> > like having the top-level "debian" directory for debian packaging stuff.
>
> You should talk to Alan Carvalho de Assis.  It has been his dream for a
> long time to get a NuttX package building system (like the original
> Buildroot or OpenEmbedded) for NuttX.  The apps/ directory build
> framework might be a starting point but I don't think anyone has done
> anything like that other than just talk about what a good idea it is.
>
>
>
>

Re: how to port things from spresense sdk

[Gregory Nutt <sp...@gmail.com>]

>>> How about we host the active project porting on github.com/nuttx? so
>>> the community could share the work.
>> The ideal solution would be to have the Pahu MQTT support NuttX natively
>> in their code.  Then you do not have to port it at all.  We don't want
>> responsibility for maintaining forks of other people's code.  It is a
>> large effort that takes a lifetime commitment.  We have never done a
>> good job trying that in the past.
> i agree it's ideal.
> is there a "canonical" way for a software to have native nuttx support?
> like having the top-level "debian" directory for debian packaging stuff.

You should talk to Alan Carvalho de Assis.  It has been his dream for a 
long time to get a NuttX package building system (like the original 
Buildroot or OpenEmbedded) for NuttX.  The apps/ directory build 
framework might be a starting point but I don't think anyone has done 
anything like that other than just talk about what a good idea it is.

Re: how to port things from spresense sdk

[Takashi Yamamoto <ya...@midokura.com.INVALID>]

On Tue, Feb 11, 2020 at 12:34 AM Gregory Nutt <sp...@gmail.com> wrote:
>
>
> > How about we host the active project porting on github.com/nuttx? so
> > the community could share the work.
> The ideal solution would be to have the Pahu MQTT support NuttX natively
> in their code.  Then you do not have to port it at all.  We don't want
> responsibility for maintaining forks of other people's code.  It is a
> large effort that takes a lifetime commitment.  We have never done a
> good job trying that in the past.

i agree it's ideal.
is there a "canonical" way for a software to have native nuttx support?
like having the top-level "debian" directory for debian packaging stuff.

Re: how to port things from spresense sdk

[Gregory Nutt <sp...@gmail.com>]

> How about we host the active project porting on github.com/nuttx? so
> the community could share the work.
The ideal solution would be to have the Pahu MQTT support NuttX natively 
in their code.  Then you do not have to port it at all.  We don't want 
responsibility for maintaining forks of other people's code.  It is a 
large effort that takes a lifetime commitment.  We have never done a 
good job trying that in the past.

Re: how to port things from spresense sdk

[Xiang Xiao <xi...@gmail.com>]

How about we host the active project porting on github.com/nuttx? so
the community could share the work.

On Mon, Feb 10, 2020 at 11:11 PM Gregory Nutt <sp...@gmail.com> wrote:
>
>
> > I wanted to use mqtt on nuttx.
> > I found a nuttx port of paho.mqtt.embedded-c in spresense sdk. [1]
> > I modified it for my nuttx $(APPDIR)/external.
> > you can find it here: https://github.com/yamt/mqtt_nuttx
> > while it worked, i'm not quite happy with having a fork like this.
> > can anyone suggest a better way? thank you.
> We cannot maintain a fork of an active project either.  There really is
> no better way.  This is part of your application suite, not part of NuttX.

Re: how to port things from spresense sdk

[Gregory Nutt <sp...@gmail.com>]

> I wanted to use mqtt on nuttx.
> I found a nuttx port of paho.mqtt.embedded-c in spresense sdk. [1]
> I modified it for my nuttx $(APPDIR)/external.
> you can find it here: https://github.com/yamt/mqtt_nuttx
> while it worked, i'm not quite happy with having a fork like this.
> can anyone suggest a better way? thank you.
We cannot maintain a fork of an active project either.  There really is 
no better way.  This is part of your application suite, not part of NuttX.