I can't comment on the version of FreeBasic required to compile gcbasic.bas, you may have a point there, all I can say is that an executeable was built by that version of FreeBasic, it ran on my Windows 10 machine and created a file from the source which required the most recent version due to an issue with variable names.
Have you you tested? AVR? PIC? LGT? Testing is crutial to Great Cow BASIC and the quality of the ASM and HEXs created.
Did I share the command line parameters use to compile ? I am not sure Hugh or I have published in the Help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If there is a real need for an unmanaged minimal build then so be it. Make a request on GCBASIC.
- we will need to change the source so we know when trying to do support that this is an unmanaged compiler (the first thing the user should do is update to the latest build upon an error).
- when we doing a fix - we would have get the user to use gcstudio or for them to extract from gcstudio Dev Channel
Re Freebasic. We complete 1000s of automated tests on the compiler on every build. The only version that is support is the version in Files. I will now add a new piece of data to the ASM to shown the version of FBC being used to compile the GCBASIC compiler. Any other version will not be supported.
Re SVN is only consistent upon a build. Only use the release toolchain.
Re Reserved Words - only use the file in the latest build.
Re Virus checking. That is a fact. The exe is whitelisted as is the rest of the toolchain.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The need for a minimum components solution will create an amount of work.
Assuming this is needed then we would need a PIC and & AVG/LGT build.
We would need to provide a programming toolchain.
We would build inline with the MainStream build program.
The PIC would need GREATCOWBASIC folder and all the PIC programmers. And PREFS EDITOR & USE.INI would need to handle a PIC only build plus PICINFO
The AVR/LGT would need GREATCOWBASIC folder and all the AVR programmers. And PREFS EDITOR & USE.INI would need to handle a PIC only build plus AVRINFO
This is a huge amount of work.
@mkstevo I could write a batch file that updates your setup from a GCSTUDIO build. Or, you could give us your GEANY setup as the MASTER GEANY setup for the inclusion in the build.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the response.
I have decided to remove my instructions following the negative comments.
I have no desire to derail GCBasic, GCStudio or GC Code. Equally I have no desire to generate work for anyone, especially when they've been exceptionally generous, patient and kind in assisting me in the past.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi mkstevo, I can’t see your posts, I just see the same one repeating again, well in any case I can suggest you an option to compile your own version from source of the compiler with the latest toolchain, current and tested source and tested Free Basic compiler.
Well, maybe you doesn’t going to like it, but there it goes:
Since GCstudio 1.00 the source code is embedded on the solution and an integrated environment is offered as a turn key solution to ease the learning curve for new contributors.
This have various advantages for new developers and for experimentation, because by default GCstudio will return automatically to the release build upon restart (you can change this behavior if desired) also, on every update the source code will be automatically updated to the current one and you can reset the changes made to the source if needed.
To enter is very easy: (you MUST be on mainstream channel, if not, select it and click on force update first.)
Open GCstudio and go to settings and click on “GCB Compiler” under GCB Integrated Development (see pic)
The GCB Compiler project will be opened, click on gcbasic.bas (or any other source file) on the solution explorer and edit as you desire, then a new option will be available on the tasks (f4) click on “Build GCB Compiler” the compiler will be built with your changes. (see previous pic)
You can open any gcb project to test your new build, and the compiler automatically will be back to the official release upon restart of GCstudio.
If you wish to disable the go back function, just go to settings and change Compiler Architecture from “Auto” or any other you have, to “Developper”, also if you don’t want to get the source updated, you can select “no updates” on the Update Channel”
If some one are interested, I can make a quick video.
Further information: only main releases contain updates to the source code, so you will have the stable and approved source even if you are on dev preview channel (dev or testing source is not distributed on any updates)
Because of this is IMPORTANT that you stay on main stream channel if you want to compile your code, this will ensure that you have a consistent tool-chain and source code.
I repeat, DONT BUILD THE COMPILER WHILE ON DEV PREVIEW CHANNEL unless you know what you are doing.
Last edit: Angel Mier 2022-12-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Have you you tested? AVR? PIC? LGT? Testing is crutial to Great Cow BASIC and the quality of the ASM and HEXs created.
Did I share the command line parameters use to compile ? I am not sure Hugh or I have published in the Help.
Just posted. https://sourceforge.net/p/gcbasic/discussion/596084/thread/2f0beef127/?page=19&limit=25#29f6/8b0b
See 'Even this harms you and your work, you are a contributor of this project, don’t spit upwards'
Guys.
Let me help
If there is a real need for an unmanaged minimal build then so be it. Make a request on GCBASIC.
- we will need to change the source so we know when trying to do support that this is an unmanaged compiler (the first thing the user should do is update to the latest build upon an error).
- when we doing a fix - we would have get the user to use gcstudio or for them to extract from gcstudio Dev Channel
Re Freebasic. We complete 1000s of automated tests on the compiler on every build. The only version that is support is the version in Files. I will now add a new piece of data to the ASM to shown the version of FBC being used to compile the GCBASIC compiler. Any other version will not be supported.
Re SVN is only consistent upon a build. Only use the release toolchain.
Re Reserved Words - only use the file in the latest build.
Re Virus checking. That is a fact. The exe is whitelisted as is the rest of the toolchain.
The need for a minimum components solution will create an amount of work.
Assuming this is needed then we would need a PIC and & AVG/LGT build.
We would need to provide a programming toolchain.
We would build inline with the MainStream build program.
The PIC would need GREATCOWBASIC folder and all the PIC programmers. And PREFS EDITOR & USE.INI would need to handle a PIC only build plus PICINFO
The AVR/LGT would need GREATCOWBASIC folder and all the AVR programmers. And PREFS EDITOR & USE.INI would need to handle a PIC only build plus AVRINFO
This is a huge amount of work.
@mkstevo I could write a batch file that updates your setup from a GCSTUDIO build. Or, you could give us your GEANY setup as the MASTER GEANY setup for the inclusion in the build.
Thanks for the response.
I have decided to remove my instructions following the negative comments.
I have no desire to derail GCBasic, GCStudio or GC Code. Equally I have no desire to generate work for anyone, especially when they've been exceptionally generous, patient and kind in assisting me in the past.
Hi mkstevo, I can’t see your posts, I just see the same one repeating again, well in any case I can suggest you an option to compile your own version from source of the compiler with the latest toolchain, current and tested source and tested Free Basic compiler.
Well, maybe you doesn’t going to like it, but there it goes:
Since GCstudio 1.00 the source code is embedded on the solution and an integrated environment is offered as a turn key solution to ease the learning curve for new contributors.
This have various advantages for new developers and for experimentation, because by default GCstudio will return automatically to the release build upon restart (you can change this behavior if desired) also, on every update the source code will be automatically updated to the current one and you can reset the changes made to the source if needed.
To enter is very easy:
(you MUST be on mainstream channel, if not, select it and click on force update first.)
Open GCstudio and go to settings and click on “GCB Compiler” under GCB Integrated Development (see pic)
The GCB Compiler project will be opened, click on gcbasic.bas (or any other source file) on the solution explorer and edit as you desire, then a new option will be available on the tasks (f4) click on “Build GCB Compiler” the compiler will be built with your changes. (see previous pic)
You can open any gcb project to test your new build, and the compiler automatically will be back to the official release upon restart of GCstudio.
If you wish to disable the go back function, just go to settings and change Compiler Architecture from “Auto” or any other you have, to “Developper”, also if you don’t want to get the source updated, you can select “no updates” on the Update Channel”
If some one are interested, I can make a quick video.
Angel
Last edit: Angel Mier 2022-12-17
Further information: only main releases contain updates to the source code, so you will have the stable and approved source even if you are on dev preview channel (dev or testing source is not distributed on any updates)
Because of this is IMPORTANT that you stay on main stream channel if you want to compile your code, this will ensure that you have a consistent tool-chain and source code.
I repeat, DONT BUILD THE COMPILER WHILE ON DEV PREVIEW CHANNEL unless you know what you are doing.
Last edit: Angel Mier 2022-12-17
there you go.
You Tube Video:
Playing with the source code of the compiler on GC Studio
As always, sorry for my English.
Angel