gnupic: Thread: pic30.googlecode.com

Hi,

I'm tracking GPL sources from MPLAB C30 (+C32?) on
http://pic30.googlecode.com/
The idea is to have code & patches, rather than just patches.

The current 3.24 branch simply accumulates the usual patches.  My
preliminary outlook is that most of the patches look like overkill -- that a
more minimal patch set for a successful build and install following the MCHP
layout (i.e. /opt/microchip) would be a better idea.

My next step would be to copy the new "gcc-4.0.3" (not the mysterious
"gcc-4.0.2/gcc-4.0.2") structure from /branches/v3_24/ into /trunk/, revert
sources to MCHP originals, generate minimal patches to build, update
installation to reflect an /opt/microchip structure, and then to compare
this with an MCHP LITE Linux install.

The ultimate objective is to be able to match sources to binaries reliably,
and ideally to fix bugs.

Anyone interested in lending a hand is most welcome.

--John

-- 
http://www.google.com/profiles/john.douglas.pritchard

Good effort John!

Cheers
/Ake

John Pritchard skrev 2011-01-22 14:45:
> Hi,
>
> I'm tracking GPL sources from MPLAB C30 (+C32?) on
> http://pic30.googlecode.com/
> The idea is to have code&  patches, rather than just patches.
>
> The current 3.24 branch simply accumulates the usual patches.  My
> preliminary outlook is that most of the patches look like overkill -- that a
> more minimal patch set for a successful build and install following the MCHP
> layout (i.e. /opt/microchip) would be a better idea.
>
> My next step would be to copy the new "gcc-4.0.3" (not the mysterious
> "gcc-4.0.2/gcc-4.0.2") structure from /branches/v3_24/ into /trunk/, revert
> sources to MCHP originals, generate minimal patches to build, update
> installation to reflect an /opt/microchip structure, and then to compare
> this with an MCHP LITE Linux install.
>
> The ultimate objective is to be able to match sources to binaries reliably,
> and ideally to fix bugs.
>
> Anyone interested in lending a hand is most welcome.
>
> --John
>

lördagen den 22 januari 2011 skrev John Pritchard:
> Hi,
>
> I'm tracking GPL sources from MPLAB C30 (+C32?) on
> http://pic30.googlecode.com/
<<cut>>
> Anyone interested in lending a hand is most welcome.
>
> --John

I have, after more work than I wanted to put in (isn't it always like that?), 
got 3.25 working. I have used a mixture of patches available on the net and 
some of my own. There is a bug too, which shows up as botched search paths. I 
have removed some windows stuff and moved the header files and libraries to a 
more linux place  /usr/share/pic30/{include,lib,gld,inc}.

Right now I have put the Microchip stuff there, for testing, but I will 
probably remove it all, and replace with open-source stuff for the pic30 
part(s) that I  use, due to copyright reasons.

The question here is exactly which parts are GPL and which are copyrighted? 

Karro

Hi Karro,

One assumes that everything in the tarball is copyrighted & GPL, according
to GPL rules.

I've added you (and Ake) to the committers list @
http://pic30.googlecode.com/ in case you'd like to create a 3.25 branch.

Cheers,
John


On Sat, Jan 29, 2011 at 3:41 AM, Karolina ####@####.####

> lördagen den 22 januari 2011 skrev John Pritchard:
> > Hi,
> >
> > I'm tracking GPL sources from MPLAB C30 (+C32?) on
> > http://pic30.googlecode.com/
> <<cut>>
> > Anyone interested in lending a hand is most welcome.
> >
> > --John
>
> I have, after more work than I wanted to put in (isn't it always like
> that?),
> got 3.25 working. I have used a mixture of patches available on the net and
> some of my own. There is a bug too, which shows up as botched search paths.
> I
> have removed some windows stuff and moved the header files and libraries to
> a
> more linux place  /usr/share/pic30/{include,lib,gld,inc}.
>
> Right now I have put the Microchip stuff there, for testing, but I will
> probably remove it all, and replace with open-source stuff for the pic30
> part(s) that I  use, due to copyright reasons.
>
> The question here is exactly which parts are GPL and which are copyrighted?
>
> Karro
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>


-- 
http://www.google.com/profiles/john.douglas.pritchard

/opt/microchip
/opt/microchip/asm30
/opt/microchip/asm30/bin
/opt/microchip/asm30/bin/bin
/opt/microchip/asm30/support
/opt/microchip/asm30/support/dsPIC30F
/opt/microchip/asm30/support/dsPIC33F
/opt/microchip/asm30/support/generic
/opt/microchip/asm30/support/PIC24F
/opt/microchip/asm30/support/PIC24H
/opt/microchip/asm30/support/templates
/opt/microchip/mpasm
/opt/microchip/mpasm/bin
/opt/microchip/mpasm/bin/LKR
/opt/microchip/mpasm/etc
/opt/microchip/mpasm/installation
/opt/microchip/mpasm/lib
/opt/microchip/mpasm/lib/perl
/opt/microchip/mpasm/lib/python
/opt/microchip/mpasm/lib/wine
/opt/microchip/mpasm/share
/opt/microchip/mpasm/share/crossover
/opt/microchip/mpasm/share/icons
/opt/microchip/mpasm/share/images
/opt/microchip/mpasm/share/locale
/opt/microchip/mpasm/share/wine
/opt/microchip/mpasm/support
/opt/microchip/mpasm/support/desktopdata
/opt/microchip/mpasm/support/mpasm
/opt/microchip/mplabc30
/opt/microchip/mplabc30/v3.24
/opt/microchip/mplabc30/v3.24/bin
/opt/microchip/mplabc30/v3.24/errata-lib
/opt/microchip/mplabc30/v3.24/include
/opt/microchip/mplabc30/v3.24/lib
/opt/microchip/mplabc30/v3.24/src
/opt/microchip/mplabc30/v3.24/support
/opt/microchip/mplabc32
/opt/microchip/mplabc32/v1.11a
/opt/microchip/mplabc32/v1.11a/bin
/opt/microchip/mplabc32/v1.11a/doc
/opt/microchip/mplabc32/v1.11a/lib
/opt/microchip/mplabc32/v1.11a/pic32-libs
/opt/microchip/mplabc32/v1.11a/pic32mx
/opt/microchip/mplab_ide
/opt/microchip/mplab_ide/bin
/opt/microchip/mplab_ide/cnd
/opt/microchip/mplab_ide/cnd/bin
/opt/microchip/mplab_ide/cnd/config
/opt/microchip/mplab_ide/cnd/modules
/opt/microchip/mplab_ide/cnd/update_tracking
/opt/microchip/mplab_ide/dlight
/opt/microchip/mplab_ide/dlight/config
/opt/microchip/mplab_ide/dlight/modules
/opt/microchip/mplab_ide/dlight/tools
/opt/microchip/mplab_ide/dlight/update_tracking
/opt/microchip/mplab_ide/etc
/opt/microchip/mplab_ide/harness
/opt/microchip/mplab_ide/harness/antlib
/opt/microchip/mplab_ide/harness/config
/opt/microchip/mplab_ide/harness/etc
/opt/microchip/mplab_ide/harness/jnlp
/opt/microchip/mplab_ide/harness/launchers
/opt/microchip/mplab_ide/harness/modules
/opt/microchip/mplab_ide/harness/nbi
/opt/microchip/mplab_ide/harness/testcoverage
/opt/microchip/mplab_ide/harness/update_tracking
/opt/microchip/mplab_ide/ide
/opt/microchip/mplab_ide/ide/bin
/opt/microchip/mplab_ide/ide/config
/opt/microchip/mplab_ide/ide/docs
/opt/microchip/mplab_ide/ide/jsstubs
/opt/microchip/mplab_ide/ide/modules
/opt/microchip/mplab_ide/ide/update_tracking
/opt/microchip/mplab_ide/mdbcore
/opt/microchip/mplab_ide/mdbcore/config
/opt/microchip/mplab_ide/mdbcore/modules
/opt/microchip/mplab_ide/mdbcore/update_tracking
/opt/microchip/mplab_ide/mplab_ide
/opt/microchip/mplab_ide/mplab_ide/config
/opt/microchip/mplab_ide/mplab_ide/core
/opt/microchip/mplab_ide/mplab_ide/modules
/opt/microchip/mplab_ide/mplab_ide/update_tracking
/opt/microchip/mplab_ide/mplablibs
/opt/microchip/mplab_ide/mplablibs/config
/opt/microchip/mplab_ide/mplablibs/modules
/opt/microchip/mplab_ide/mplablibs/update_tracking
/opt/microchip/mplab_ide/nb
/opt/microchip/mplab_ide/nb/config
/opt/microchip/mplab_ide/nb/core
/opt/microchip/mplab_ide/nb/modules
/opt/microchip/mplab_ide/nb/update_tracking
/opt/microchip/mplab_ide/platform
/opt/microchip/mplab_ide/platform/config
/opt/microchip/mplab_ide/platform/core
/opt/microchip/mplab_ide/platform/docs
/opt/microchip/mplab_ide/platform/lib
/opt/microchip/mplab_ide/platform/modules
/opt/microchip/mplab_ide/platform/update_tracking

lördagen den 29 januari 2011 skrev John Pritchard:
> Hi Karro,
>
> One assumes that everything in the tarball is copyrighted & GPL, according
> to GPL rules.

Which means that it does not work properly, since c30_device.info is not 
included. Or rather, that it works in a generic mode, -mcpu=generic-16bit.
I am not sure exactly what that means practically. If the generic mode is 
usable, or unusable.

I particularly don't like the c30_device.info dependance. It should be 
relatively easy to replace it with a readable/editable ascii-file with the 
same information, since the interface is localised. 

An interesting line of work.. perhaps I'm lazy when I presume the awkward
dependence on the nonfree MCHP material..

On Sat, Jan 29, 2011 at 8:17 AM, Karolina Lindqvist <
####@####.#### wrote:

> lördagen den 29 januari 2011 skrev John Pritchard:
> > Hi Karro,
> >
> > One assumes that everything in the tarball is copyrighted & GPL,
> according
> > to GPL rules.
>
> Which means that it does not work properly, since c30_device.info is not
> included. Or rather, that it works in a generic mode, -mcpu=generic-16bit.
> I am not sure exactly what that means practically. If the generic mode is
> usable, or unusable.
>
> I particularly don't like the c30_device.info dependance. It should be
> relatively easy to replace it with a readable/editable ascii-file with the
> same information, since the interface is localised.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>


-- 
http://www.google.com/profiles/john.douglas.pritchard