View previous topic :: View next topic |
Author |
Message |
Ttelmah
Joined: 11 Mar 2010 Posts: 19358
|
|
Posted: Fri Jan 28, 2022 12:49 pm |
|
|
Good. That matches the behaviour I have seen on some other things.
My 'belief' if that the compiler works always sequentially.
Stuff in the command line is treated as if it is typed in front of the first
line of the actual program.
So if you specify a define in the command line for example, it is defined,
but if there is a different define in the code you get up the warning saying
that this has been redefined. |
|
![](templates/subSilver/images/spacer.gif) |
pmuldoon
Joined: 26 Sep 2003 Posts: 218 Location: Northern Indiana
|
|
Posted: Mon Jan 31, 2022 7:29 am |
|
|
Just to follow-up, I was sent a patch from CCS. I dropped it into my PICC\DLL\5.105 folder per instructions.
Now I get a compile error:
Quote: |
*** Error 44 "C:\Program Files (x86)\PICC\devices\18LF6722.h" Line 11(1,1): Internal Error - Contact CCS PR-CODE at 85/C/0 SCR=294
|
CCS requested my source, so I sent it along with a copy of the header file that was rejected. They said it compiled fine for them and asked what my latest compiler version is (5.105). No indication of what would cause the error other than saying it's not a license issue.
Has anyone ever seen that error? I'm sure CCS will resolve it, but I'm going to have to move fwd today, even if it means using the original compiler and changing to #OPT 0 and hoping nothing else breaks in the downshift. Or stepping back to the original compiler version.
BTW, what is the best way to temporarily switch to a previous compiler version? I have a PICC\DLL\ folder full of #.## folders (for each version upgrade). I use both MPLAB8 and MPLABX. Is there something in the myriad features I don't use that would handle this? A compiler directive would be really cool, #COMPILER 5.105, but I'm sure that's to easy a solution. Really, it should be a directive option so that every program would be 'locked' to the compiler version it was created in until the user decided otherwise. |
|
![](templates/subSilver/images/spacer.gif) |
Ttelmah
Joined: 11 Mar 2010 Posts: 19358
|
|
Posted: Mon Jan 31, 2022 7:48 am |
|
|
The compiler does have an option to compile with older versions.
However 'caveat', you will still have the current include files etc..
I've always installed each CCS version into a separate directory, so
that I can specify the version and keep it with each project for this
reason. |
|
![](templates/subSilver/images/spacer.gif) |
pmuldoon
Joined: 26 Sep 2003 Posts: 218 Location: Northern Indiana
|
|
Posted: Mon Jan 31, 2022 8:23 am |
|
|
Just looking at the .h file, there is no revision reference within it. So there is no way to tell what compiler version it is associated with. They are small but many, so it would be impractical to save them all.
I suppose one could add a version suffix to the header filename and save it with the project, then somehow reference the desired compiler folder.
Somewhere along the line these dev environments missed the obvious. If you can't lock-in a compiler revision, then full, functional testing is required every time the compiler is upgraded. And who does, or wants to do that?
I guess I've just turned into one of those old guys who just complains a lot, LOL. |
|
![](templates/subSilver/images/spacer.gif) |
temtronic
Joined: 01 Jul 2010 Posts: 9168 Location: Greensville,Ontario
|
|
Posted: Mon Jan 31, 2022 10:39 am |
|
|
re: I guess I've just turned into one of those old guys who just complains a lot, LOL.
cheer up, someone installed a fancy router for my old trusty one and I don't get emails for 3 days !!! Reinstall old router, 42 come in real fast but...wife HAS to have wireless for here inbed netflix..
.
sigh.. I'm tired of this new 'tech'..
let's bring back the PIC16C84 !!!
Jay |
|
![](templates/subSilver/images/spacer.gif) |
Ttelmah
Joined: 11 Mar 2010 Posts: 19358
|
|
Posted: Mon Jan 31, 2022 11:08 am |
|
|
I still have a couple of boards out on site running with those!. Remember
their amazement when I said it didn't have a millennium issue. Seems
an age ago now....
Unfortunately CCS recently seem to have stepped back a little in their
QA on new versions. A definite caveat.
A couple of years ago, they produced a number of versions without
seeming to introduce many new bugs. Recently issues are not being
fixed as well as they were and seem to come with a lot of new issues. |
|
![](templates/subSilver/images/spacer.gif) |
pmuldoon
Joined: 26 Sep 2003 Posts: 218 Location: Northern Indiana
|
|
Posted: Mon Jan 31, 2022 12:38 pm |
|
|
Would either of you guys be interested in buying a slightly used UV eraser and some windowed 16c56/57 chips, LOL!
I remember I just used to keep the lamp running all day while I swapped chips and debugged my programs. |
|
![](templates/subSilver/images/spacer.gif) |
Ttelmah
Joined: 11 Mar 2010 Posts: 19358
|
|
Posted: Wed Feb 02, 2022 6:46 am |
|
|
I still have my own eraser, and many hundreds of the old windowed
chips... |
|
![](templates/subSilver/images/spacer.gif) |
|