Re: [jallib] JALLIB sample fails to compile

[Sunish Issac]

I'm able to compile both the samples with the jalpack version that's included with jaledit. No errors/warnings.
Did you inadvertently  replace the include files ?

Sunish

On Tue, Jul 24, 2012 at 2:48 AM, sstandfast <sstan...@gmail.com> wrote:

18F27j13

[Rob Hamerling]

Hi Shawn,

On 07/23/12 11:18 pm, sstandfast wrote:
> This is a re-post of an issue I reported over on JALLIST. I thought this forum might be a little more appropriate being JALLIB specific. Some additional information; the 18F27j13 is not the only sample I'm having trouble with apparently. I also get the same 7 errors when trying to compile the 18F27j53_blink.jal. So far it appears that any PIC with a second letter in the name, the sample code will not compile. The 18F14K22_blink.jal sample fails with 3 errors:

If it is about Jallib libraries or ssamples, indeed this group is the
place to report!

> Compilation started at :7/23/2012 4:09:31 PM
> jal 2.4o (compiled May 8 2011)
> [Error] (lib/18f14k22.jal) [Line 1098] "pps_0" not defined
> [Error] (lib/18f14k22.jal) [Line 1098] constant expression expected
> [Error] (lib/18f14k22.jal) [Line 1098] '=' expected (got 'procedure')

PPS_0 is defined in constants_jallib.jal.
Every Jallib device file includes chipdef_jallib, which on its turn
includes constants_jallib, and all these files are in the lib directory
which comes with jalpack. So it looks like you have 'manipulated' your
library setup.


> I'm having an issue with getting a "blink" sample from JALLIB to successfully
> compile. I am trying to get the 18F27j13_blink.jal to compile but it keeps
> throwing the following errors:
>
> Compilation started at :7/19/2012 2:48:39 PM
> jal 2.4o (compiled May 8 2011)
> [Error] (lib/18f27j13.jal) [Line 48] 'pic_18f27j13' not found
> [Error] (lib/18f27j13.jal) [Line 1894] "adc_v11_1" not defined
> [Error] (lib/18f27j13.jal) [Line 1894] constant expression expected
> [Error] (lib/18f27j13.jal) [Line 1894] '=' expected (got 'const')

Same story.


> I can compile other examples just fine but the 18f27j13 sample is broken.
> Please help. I am using the following build of JALLIB: jallib-pack-2.4o-0.8.0

All samples compile fine here, so none broken, but your setup!

Regards, Rob.


--
R. Hamerling, Netherlands --- http://www.robh.nl

[Sebastien Lelong]

Buildbot reported: « if build was a success then all samples compile fine»

Cheers
Seb

--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.
To unsubscribe from this group, send email to jallib+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jallib?hl=en.

[sstandfast]

As far as I know the setup should be pretty straight forward. I downloaded the zip file, extracted it, opened JALEDIT and pointed it to the compiler/library directory and tried a sample. Now I do have two different revisions of JALLIB in this directory but they only share the top level folder. Other than that they are independent. I will perform a fresh extraction and see if that makes a difference. If not, perhaps removing the previous version of JALLIB might help.

Three funny thing is, in JALEdit, I can double click on the errors and be taken right to the error in the include file, open the chipdef file, ctrl+f and find the"missing" definition. Makes me wonder if somehow the compiler is still looking in the old directory for some reason. Anyone else had success with two (or more) versions of JALLIB in the same directory?

I'll post back when I have more info.

Shawn

[Sunish Issac]

jaledit opens the first file matching the filename in the order provided in search folder list.

Sunish 

--
You received this message because you are subscribed to the Google Groups "jallib" group.

To view this discussion on the web visit https://groups.google.com/d/msg/jallib/-/Moxdk4Po72oJ.

To post to this group, send email to jal...@googlegroups.com.

To unsubscribe from this group, send email to jallib+un...@googlegroups.com.