Hi Jim, You would only need to compile it when there is a new version of the compiler available. You may upload it to github at tools/compiler/jalv2_pi_2.4q5/
What file name will you use? "jalv2pi"? A small text doc on how to compile it would be nice as well. If it's on Github, i'll be able to find it when I create the next package. I'll likely only add it to the package if the version on github is the most recent version of the compiler. Obviously we don't want to use an out of date compiler. It would be a good contribution. Thanks, Matt. On Wednesday, June 15, 2016 at 6:50:42 AM UTC-4, Jim Gregory wrote: > > I'm assuming the only time it would need to be recompiled is when Kyle > releases a new version of the compiler, not each new release of jallib. If > that is correct, then I'd be willing to compile it (since I'm going to have > to do it for myself anyway :) ), but only if it doesn't add an extra burden > for you. > > As for as the directory structure goes, are you proposing to leave the > 'mainstream' Windows, OS X, and Linux x86 binaries in the jalv2/compiler > directory as they are now, and put the others (Raspberry Pi, eComStation, > etc.) in the tools directory? That seems a bit unintuitive to me, since as > a new user, I'd expected to find all the compiled versions in the compiler > directory. > > -Jim > > > > On Monday, June 13, 2016 at 4:45:35 PM UTC-5, Matthew Schinkel wrote: >> >> 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 jallib+unsubscr...@googlegroups.com. To post to this group, send email to jallib@googlegroups.com. Visit this group at https://groups.google.com/group/jallib. For more options, visit https://groups.google.com/d/optout.
