srvaldez has 'pulled' the builds at the link below. The following can still be used, but we must use other builds.
Go to the opening post of FreeBASIC-1.06.0-Win gcc-9.1.
Now download the 32-bit and 64-bit of the gcc compilers that you may want to use from the list headed 'more builds from git 2019-08-23'. I qualify as being barking mad, so I downloaded all of them. <smile>
Open WinFBE and navigate to Options>Environment Options...>Compiler Setup and copy the FBC 32-bit and 64-bit entries. Needless to say I very much hope that you will not need to restore these entries but it is better to be safe than sorry.
NOTE: SetGCCVersion has been changed to SetGCCforWinFBE ( 2 Sept 2019) - see later post.
'SetGCCVersion' needs an ini file and you will have to write it. What? Shut up and just do it.
This is what mine looks like:
Code: Select all
"5.2", "C:\Program Files (x86)\FreeBASIC\fbc.exe", "E:\Downloads\FreeBASIC-1.07.0-win64\fbc.exe"
"7.4", "E:\Downloads\fb107-win32-gcc740\FreeBASIC-1.07.0-win32\fbc.exe", "E:\Downloads\fb107-win64-gcc740\FreeBASIC-1.07.0-win64\fbc.exe"
"8.3", "E:\Downloads\fb107-win32-gcc830\FreeBASIC-1.07.0-win32\fbc.exe", "E:\Downloads\fb107-win64-gcc830\FreeBASIC-1.07.0-win64\fbc.exe"
"9.2", "E:\Downloads\fb107-win32-gcc920\FreeBASIC-1.07.0-win32\fbc.exe", "E:\Downloads\fb107-win64-gcc920\FreeBASIC-1.07.0-win64\fbc.exe"
The first entry is the path to WinFBE's ini file. You will find this in WinFBE's 'Settings' folder. The safest way to get the path is to hold a shift key down, right click on WinFBE.ini and choose, if available, 'Copy as path'.
The second and subsequent entries are in three parts. The first part is a description of the compiler. As you can see my descriptions are short and sweet. The second and third parts are the paths to the 32-bit and 64-bit paths respectively. 'SetGCCVersion.ini' should have at most four sets of paths and 'SetGCCVersion.exe' will display four radio buttons. If, for example, you only supply two sets, then the last two radio buttons will be disabled. I have just realized that I do not check that you have supplied no more than four sets, tch, tch. I will think on that one, so make sure that you do not supply more than four sets.
I have installed fbc 1.07 and the 64-bit version via Version 1.07.0 released and that is where the 5.2 paths come from.
When done save as SetGCCVersion.ini.
I write sparse forms and do not use buttons which duplicate tasks. 'setGCCVersion.exe' is bereft of buttons. If we close the form WinFBE.ini will remain as found, effectively cancelling the form. We will do this if the current compiler is what we actually want. If we select a radio button WinFBE.ini will be edited accordingly, and we just close the form.
This is what I get running 'SetGCCVersion.exe', indicating that the current compiler used is 8.3. If I am happy with that then I would just close the form otherwise I would choose another compiler and then close the form.
When SetGCCVersion runs it will try to match the current 32-bit compiler path in WinFBE.ini with the second part of each of the compilers paths in 'SetGCCVersion.ini'. If successful then the appropriate radio button will be set. If it fails to match then a message box will display "Could not determine existing setup". This will, undoubtedly, occur on the very first run of 'SetGCCVersion.exe'. Don't worry, just click on the compiler you wish to use; on subsequent runs of 'SetGCCVersion.exe' you should see a set radio button indicating the current compiler used.
'SetGCCVersion.exe' runs TopMost.
Some of you rascals will probably try to run 'SetGCCVersion.exe' more than one once. You can try it but it won't get you anywhere - I have blocked you. <smile>
Any problems with 'SetGCCVersion.exe' then please let me know. I will put money on it that you will. Step 2 should get you out of trouble.
You can thank me for this if you want but, believe me, I would not be the slightest bit upset if you didn't. What I have done here pale into insignificance compared with srvaldez's monumental task of providing us with a rich set of gcc compilers to choose from. While I am at it, and not mentioned enough, is ST_W's fbc builds, coderJeff knocking two fbc versions in the same year and fxm updating the Help file at the drop of a hat. Oh, and counting_pine who probably does a lot more than we think he does. Have I missed anyone out? I sometimes regret my 'having a go' at both coderJeff and counting_pine some time ago resulting in my departing to the hills for a while but I do have a short temper. Of course, we got Imortis as a Moderator out of it so there was a good side. Blimey, it took me a long time to divulge that. <smile>
I cannot remember when I first tried gcc 7.3, from a srvaldez build, but found that the 64-bit version was a tad unreliable. I am finding the same with 7.4. The more people experimenting with 7.4 the better because if it turns out that it is unreliable for others then that would be worthwhile for coderJeff to hear about it as version 7 looks to be the likeliest version to become the 'official line'. gcc 8.3 may be a better option. WinFBE's default is 8.1 and I have found that to be stable.