On 05/28/2015 03:13 PM, Neil wrote:

First my work is not in electronics, it's systems (software) testing.
So take that with a grain of salt. Also I use the Arduino community
for play though it is working well (with my Smart Home Automation Cloud
Internet of Things - did I just get bingo?).

> But I recently started looking into PIC32's again, and thought I'd use a
> Chipkit that I have here as a dev board (without the Chipkit software
> and bootloader, so I would use MPLAB etc).  But as Chipkit, Teensy, and
> others are becoming more and more popular, and the *duino IDEs are
> getting mature, it's becoming very tempting to take advantage of the
> ease of development and just go with the MPIDE/UECIDE and associated
> libraries, especially as I'm looking into using WiFi, Bluetooth, SD
> cards, etc.  And let's be realistic -- Microchip's libraries aren't
> perfect anyway.

I've played a bit with the libraries (Porting to MPIDE from Arduino)
and I'm not overly fond of the way some libraries are written (byte
to int to pointer conversions that are questionable). I don't think it's
bad for one offs but a run - not trusting my job to that.

> So what's the general feeling on this?  Is there a compelling reason to
> go or not-go this way?  What about the license -- I've not read the
> license yet but do I need to make my code open source?  I'm assuming I
> can set the code protection bits with MPLAB IPE, etc.

I've not tried to protect anything.

IANAL ...

I don't think you need to open source your sketch or privately written
libraries. If you fix a library I think you should share but won't
venture a guess further than that.

--=20
Linux Home Automation         Neil Cherry       ncherry@linuxha.com
http://www.linuxha.com/                         Main site
http://linuxha.blogspot.com/                    My HA Blog
Author of:    	Linux Smart Homes For Dummies
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.