I don't see how this will get into the release package. Who will be compiling this every time there is a new release?
I think it may be ok to make a directory in the tools dir for Jalv2 compiled for other systems. Documentation is good as well. Matt. On Monday, June 13, 2016 at 5:02:56 AM UTC-4, RobH wrote: > > > Hi Jim, > > On 06/12/2016 12:28 PM, Jim Gregory wrote: > > I've lately been using a Raspberry Pi 2 and Raspberry Pi 3 for my JAL > > development environment and have been very happy with it. JAL code > > compiles relatively quickly using the compiler, the Vim editor has > > syntax highlighting for JAL, I can program most chips that use > > low-voltage programming directly from the Pi's GPIO ports very quickly > > using Darren Broad's Pickle ICSP software > > (https://wiki.kewl.org/dokuwiki/projects:pickle), and I can easily > > read and write to the serial port of the PIC without an adapter using > > the Pi's serial port pins. > I have a project for RPi with PICs as slave(s). I control the RPi from > my PC over the network (VNC) and after first quick reading I didn't see > a big advantage of compiling and programming on the RPI. But after some > thought I do see advantages/opportunities now! > > > > The biggest challenge has been getting the compiler set up. JALLIB > > includes neither an ARM-compatible binary nor the source code for JAL, > > so I have to compile it from Kyle's source code and make some changes > > to get it to compile. > I have been building the compiler from the sources without problems: > - for eComStation (OS/2) using Watcom C/C++ > - to obtain a 64-bits Linux executable. > > > FWIW, the changes that are required are: > > > > 1. remove '-Werror' from one of the options in the Makefile.inc, and > > 2. add a 'bin' directory to the source code tree at the same level as > > the 'src' directory > For the 64-bits Linux version I had similar issues (and added the -O2 > option). > For eComStation I used the Watcom make utility and my own makefiles. > > > > > Would there be enough demand by users to include an ARM-compatible > > binary with JALLIB, or at least a version of the source code that > > might compiled a bit more easily for the Pi? > What is 'enough demand'? > I think it is good to add an RPi executable to Jallib, and maybe also > the ICSP facility. > > Regards, Rob. > > -- > *Rob H*amerling - http://www.robh.nl > -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/jallib. For more options, visit https://groups.google.com/d/optout.
