It wasn't actually funny at the time, but I really did have the paths wrong, and it was compiling code for a different version than I was making changes to. Actually, kind of embarrasing.
On Apr 21, 1:43 am, vasile surducan <[email protected]> wrote: > Ivan, I had always appreciate Russian humor.... > :) > > > > On Fri, Apr 20, 2012 at 5:32 PM, ivan.jal33 <[email protected]> wrote: > > on the JAL editor, click: tools-->Environment Options and check > > the paths and directories. It may not be compiling the file that you > > think it is, or the libraries, etc. > > Enjoy:) > > ivan.jal33 > > > On Apr 20, 5:00 am, vasile surducan <[email protected]> wrote: > > > It has the result of the last compile no mater if fails or not. Please > > see > > > the attached printscreen. > > > > VasileOn Thu, Apr 19, 2012 at 8:34 PM, Sunish Issac < > > [email protected]> wrote: > > > > I checked the current jalpack and the .out file is updated on each > > > > compile. I guess, you mean when compile fails, .out still has the > > results > > > > of the last compile. > > > > > Sunish > > > > > On Thu, Apr 19, 2012 at 5:06 PM, vasile surducan <[email protected] > > >wrote: > > > > >> One more about Jal edit: the file.out is not automatically rewritten > > > >> after compilation until is previously deleted. Meaning file.out must > > be > > > >> deleted after every compilation to get a newer valid file.out. > > > >> I remember this problem is very a old one and quite annoying. There is > > > >> any option for update the file.out automatically ? > > > > >> thx, > > > >> Vasile > > > > >> On Wed, Apr 18, 2012 at 6:29 PM, vasile surducan <[email protected] > > >wrote: > > > > >>> Hi Sunish, > > > >>> I've attched a printscreen. Compiler is 2.4o, history ends at 2.4l, > > not > > > >>> bad. > > > >>> I'm back to Jal after one year of pause. Happily, I forgot > > everything. > > > >>> :) > > > >>> do I see some white hear on your temple? too small picture... > > > > >>> On Wed, Apr 18, 2012 at 4:26 PM, Sunish Issac <[email protected] > > >wrote: > > > > >>>> Hello Vasile, > > > > >>>> On Wed, Apr 18, 2012 at 4:50 PM, vasile surducan < > > [email protected]>wrote: > > > > >>>>> Hi Sunish, > > > > >>>>> I've noticed at installation time there is a difference between the > > > >>>>> compiler changelog file and the compiler version in the last > > jalpack. > > > > >>>> What's the last modified date/time ? I'm not sure if something went > > > >>>> wrong with my scripts that assemble the readme files, looks like the > > > >>>> changelog is not present in the jallib distribution of compiler. > > > > >>>> Long time since I see a post of Vasile. > > > > >>>> Sunish > > > > >>>> I can't find the last compiler changelog file in the jalpack. This > > > >>>>> one:http://www.casadeyork.com/jalv2/archive/README.txt > > > >>>>> I'm looking in the wrong place? > > > > >>>>> thx, > > > >>>>> Vasile, > > > > >>>>> BTW, nice picture you have on gmail! > > > > >>>>> On Sat, Apr 7, 2012 at 6:06 AM, Sunish Issac <[email protected] > > >wrote: > > > > >>>>>> Yo can download the latest windows jalpack with jaledit from > > > >>>>>>http://code.google.com/p/jaledit/downloads/list > > > > >>>>>> Best regards, > > > >>>>>> Sunish Issac > > > > >>>>>> On Fri, Apr 6, 2012 at 11:40 PM, Z.K. <[email protected]> > > wrote: > > > > >>>>>>> I was following a tutorial that I had downloaded and it said: > > > > >>>>>>> Windows Install: > > > >>>>>>> 1. Download jalpack (installer executable) from > > > >>>>>>>http://jaledit.googlecode.com/files/JALPack_2.4_0.4_0.6.1.0.exe, > > > >>>>>>> This will install JALv2 + JalEdit > > > >>>>>>> 2. Update your installation (very important) - Download > > jallib-pack > > > >>>>>>> or > > > >>>>>>> jallib-pack-bee fromhttp://code.google.com/ > > > >>>>>>> p/jallib/downloads/list, copy the .zip contents into your Jallib > > > >>>>>>> installation directory > > > > >>>>>>> I guess the tutorial was old as well. Anyway I finally found the > > > >>>>>>> 4.60 > > > >>>>>>> and 4.62 version though neither of those has an installer for > > windows > > > >>>>>>> so I guess it means just extract it anywhere and run it from that > > > >>>>>>> directory. > > > > >>>>>>> Thanks for the info as I did not realize i was using an older > > > >>>>>>> version. Do you know if there is an updated tutorial anywhere? > > > > >>>>>>> On Apr 6, 6:13 am, Sunish Issac <[email protected]> wrote: > > > >>>>>>> > Looks like you mixed a new version of jallib and used the old > > > >>>>>>> compiler ? > > > >>>>>>> > From where did you download the jalpack ? > > > > >>>>>>> > Sunish > > > > >>>>>>> > On Fri, Apr 6, 2012 at 2:46 PM, <[email protected]> wrote: > > > >>>>>>> > > I am really new to the JAL compiler. I thought I would try a > > > >>>>>>> simple blink > > > >>>>>>> > > led from the samples. So, I created a new folder in the > > project > > > >>>>>>> folder and > > > >>>>>>> > > copied the 16F88 blink file to that folder. Then I compiled > > it > > > >>>>>>> and I got > > > >>>>>>> > > like 31 errors. Anyone have any idea what I am doing wrong. > > > > >>>>>>> > > code: > > > >>>>>>> > > include 16f88 -- target PICmicro > > > >>>>>>> > > -- > > > >>>>>>> > > -- This program assumes that a 20 MHz resonator or crystal > > > >>>>>>> > > -- is connected to pins OSC1 and OSC2. > > > >>>>>>> > > -- (unspecified configuration bits may cause a different > > > >>>>>>> frequency!) > > > >>>>>>> > > pragma target clock 20_000_000 -- oscillator frequency > > > >>>>>>> > > -- configuration memory settings (fuses) > > > >>>>>>> > > pragma target OSC HS -- HS crystal or > > > >>>>>>> resonator > > > >>>>>>> > > pragma target WDT disabled -- no watchdog > > > >>>>>>> > > pragma target DEBUG disabled -- no debugging > > > >>>>>>> > > pragma target LVP disabled -- no Low Voltage > > Programming > > > >>>>>>> > > pragma target MCLR external -- reset externally > > > >>>>>>> > > -- These configuration bit settings are only a selection, > > > >>>>>>> sufficient for > > > >>>>>>> > > -- this program, but other programs may need more or > > different > > > >>>>>>> settings. > > > >>>>>>> > > -- > > > >>>>>>> > > enable_digital_io() -- make all pins digital > > I/O > > > >>>>>>> > > -- > > > >>>>>>> > > -- Specify the pin to which the LED is connected. > > > >>>>>>> > > -- A low current (2 mA) led with 2.2K series resistor is > > > >>>>>>> recommended > > > >>>>>>> > > -- since not all pins may be able to drive an ordinary 20mA > > led. > > > >>>>>>> > > alias led is pin_A0 > > > >>>>>>> > > pin_A0_direction = output > > > >>>>>>> > > -- > > > >>>>>>> > > forever loop > > > >>>>>>> > > led = on > > > >>>>>>> > > _usec_delay(250_000) > > > >>>>>>> > > led = off > > > >>>>>>> > > _usec_delay(250_000) > > > >>>>>>> > > end loop > > > > >>>>>>> > > errors: > > > >>>>>>> > > Compilation started at :4/6/2012 1:52:27 AM > > > >>>>>>> > > jal 2.4l (compiled Aug 7 2009) > > > >>>>>>> > > [Error] (lib/16f88.jal) [Line 54] unexpected token: 'id' > > > >>>>>>> > > [Error] (lib/16f88.jal) [Line 54] "id" not defined > > > >>>>>>> > > [Error] (lib/16f88.jal) [Line 54] '=' expected (got > > '0x2000') > > > >>>>>>> > > [Error] (lib/16f88.jal) [Line 54] unexpected token: "0x2000" > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 32] unknown pragma target: > > osc > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 32] "osc" not defined > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 32] '=' expected (got 'hs') > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 32] "hs" not defined > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 32] '=' expected (got > > 'pragma') > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 33] unknown pragma target: > > wdt > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 33] "wdt" not defined > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 33] '=' expected (got > > > >>>>>>> 'disabled') > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 33] '=' expected (got > > 'pragma') > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 34] unknown pragma target: > > debug > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 34] "debug" not defined > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 34] '=' expected (got > > > >>>>>>> 'disabled') > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 34] '=' expected (got > > 'pragma') > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 35] unknown pragma target: > > lvp > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 35] "lvp" not defined > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 35] '=' expected (got > > > >>>>>>> 'disabled') > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 35] '=' expected (got > > 'pragma') > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 36] unknown pragma target: > > mclr > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 36] "mclr" not defined > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 36] '=' expected (got > > > >>>>>>> 'external') > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 36] "external" not defined > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 36] '=' expected (got > > > >>>>>>> 'enable_digital_io') > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 40] "enable_digital_io" not > > > >>>>>>> defined > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 45] "pin_a0" not defined > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 45] '=' expected (got > > > >>>>>>> 'pin_a0_direction') > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 46] "pin_a0_direction" not > > > >>>>>>> defined > > > >>>>>>> > > [Error] (16f88_blink.jal) [Line 49] "led" not defined > > > >>>>>>> > > 31 errors, 0 warnings > > > >>>>>>> > > Compiler CommandLine: > > > >>>>>>> > > C:\JALPack\compiler\jalv2.exe "C:\JALPack\project\PIC16F88 > > > >>>>>>> > > Blink\16f88_blink.jal" -s "C:\JALPack\lib" -no-variable-reuse > > > > >>>>>>> > > -- > > > >>>>>>> > > You received this message because you are subscribed to the > > > >>>>>>> Google Groups > > > >>>>>>> > > "jallib" group. > > > >>>>>>> > > To post to this group, send email to [email protected] > > . > > > >>>>>>> > > To unsubscribe from this group, send email to > > > >>>>>>> > > [email protected]. > > > >>>>>>> > > For more options, visit this group at > > > >>>>>>> > >http://groups.google.com/group/jallib?hl=en. > > > > >>>>>>> -- > > > >>>>>>> You received this message because you are subscribed to the > > Google > > > >>>>>>> Groups "jallib" group. > > > >>>>>>> To post to this group, > > ... > > read more » -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
