This is my first post.
Great gap has been been filled by you guys for PIC micro a Open source compiler.
Today i have setup the compiler. Compiler itself is working fine with compile.bat file. But when compiling with GCBIDE 1.4 is not working and it is not showing any result at all. (I am running in XP ).
The GCBIDE 1.3 is working fine. Can some boby tell me any difference between these two?..
I just started playing arround. with GC.
Let us pump more posts to this forum and extend our support to keep GC alive.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When compiling the source code there is no difference between v.1.3 and v.1.4 so it should give exactly the same results.
The main differences are:
ADDED ICPROG SUPPORT
Running of ICprog from within GCBIDE so as to speed up the process of testing the code on the chip. GCBIDE uses the internal compiler GCASM from GCBasic to produce the hex code. Hugh has gone a long way to put a stand-alone package together. My contribution is to use the internal compiler from GCBasic instead of MPASM and others. Although one can not guarantee that GCASM has no bugs, I am sure that Hugh would be very glad to here about any.
CHANGED THE SETTING OF THE COMPILER PATH ETC
The path to the compiler (GCB.EXE) has to be set to get any results. GCBIDE uses GCB.EXE to compile the code. If GCBIDE do not know where it is installed then obviously no compilation. The same for ICPROG. I have also noticed that the latest version of ICPROG requires a different time delay in the settings dialog to work correctly.
FORMAT OF PATH.CFG HAS CHANGED
The format of the path configuration file has changed so as to accommodate ICPROG.
FIXED THE BUG THAT PESTED MAINLY THE ITALIANS
GCBIDE mistakenly required GCBasic to be installed in c:\Program Files\GCBasic.
Now GCBasic can be installed anywhere as long as the path to it is set correctly.
I think your problem is that v.1.4 reads the old "path.cfg" file generated from v.1.3 . You cannot have both versions of GCBIDE in the same directory because the file format is different. The lack of documentation and a self-install package will be addressed at a later stage.
GCBIDE is only a tempory measure to make life easier while someone (Hugh) has not come up with a proper IDE for GCBasic. This is a lot of work and I think a little patience is required. GCBasic is still a work in progress.
GCBIDE has its own website at "http://gcbide.googlepages.com/home" where I will try to create more clarity.
Emile
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi guys,
This is my first post.
Great gap has been been filled by you guys for PIC micro a Open source compiler.
Today i have setup the compiler. Compiler itself is working fine with compile.bat file. But when compiling with GCBIDE 1.4 is not working and it is not showing any result at all. (I am running in XP ).
The GCBIDE 1.3 is working fine. Can some boby tell me any difference between these two?..
I just started playing arround. with GC.
Let us pump more posts to this forum and extend our support to keep GC alive.
When compiling the source code there is no difference between v.1.3 and v.1.4 so it should give exactly the same results.
The main differences are:
ADDED ICPROG SUPPORT
Running of ICprog from within GCBIDE so as to speed up the process of testing the code on the chip. GCBIDE uses the internal compiler GCASM from GCBasic to produce the hex code. Hugh has gone a long way to put a stand-alone package together. My contribution is to use the internal compiler from GCBasic instead of MPASM and others. Although one can not guarantee that GCASM has no bugs, I am sure that Hugh would be very glad to here about any.
CHANGED THE SETTING OF THE COMPILER PATH ETC
The path to the compiler (GCB.EXE) has to be set to get any results. GCBIDE uses GCB.EXE to compile the code. If GCBIDE do not know where it is installed then obviously no compilation. The same for ICPROG. I have also noticed that the latest version of ICPROG requires a different time delay in the settings dialog to work correctly.
FORMAT OF PATH.CFG HAS CHANGED
The format of the path configuration file has changed so as to accommodate ICPROG.
FIXED THE BUG THAT PESTED MAINLY THE ITALIANS
GCBIDE mistakenly required GCBasic to be installed in c:\Program Files\GCBasic.
Now GCBasic can be installed anywhere as long as the path to it is set correctly.
I think your problem is that v.1.4 reads the old "path.cfg" file generated from v.1.3 . You cannot have both versions of GCBIDE in the same directory because the file format is different. The lack of documentation and a self-install package will be addressed at a later stage.
GCBIDE is only a tempory measure to make life easier while someone (Hugh) has not come up with a proper IDE for GCBasic. This is a lot of work and I think a little patience is required. GCBasic is still a work in progress.
GCBIDE has its own website at "http://gcbide.googlepages.com/home" where I will try to create more clarity.
Emile
Thanks Man. Problem got resovled.