-shared-libgccPaulSquires wrote: The only "problem" I ran into was that the generated EXE's were huge because the runtime libraries were statically linked into the EXE.
-shared-libstdc++
Joshy
-shared-libgccPaulSquires wrote: The only "problem" I ran into was that the generated EXE's were huge because the runtime libraries were statically linked into the EXE.
You presuppose that we (me) know what we (I) are doing. :)deltarho[1859] wrote:I shall stick to random number generators and cryptography and leave graphics and toolchains to those that know what they are doing.
Code: Select all
8.3 ES 133120
8.4 WL 137216
9.3 WL 129536
10.2 WL 133632
10.2 RL 160256
10.3 WL 177152
ES Equation Solution
WL WinLibs
RL Ray Linn
srvaldez has reservations about ES and seems to be favouring WinLibs.coderJeff wrote:The equation toolchain is interesting, but I found it has some quirky behaviours when building.
Sorry David, my lack of response is certainly not an intentional lack of interest in the work that you do. Not by a long shot! I definitely appreciate big time the amount of time and effort that you pour into toolchain evaluation. I made the decision before the most previous WinFBE release to once again follow the toolchain as specified in the official FB release. This is primarily for consistency for new users to FB so that when they use WinFBE then they'll know that the compiler package backend is based on the official FB distribution. Knowing that CoderJeff is looking at changing the toolchain, you can be sure that WinFBE will follow suit.deltarho[1859] wrote:Using 8.x as fbc's new default with 5.2 as an additional will be, I reckon, welcomed by members. Having said that I do wonder at times if many members are that interested. Nearly four days ago I published some builds to add to WinFBE's V2.2.0 which had reverted to gcc 5.2 only. There has been no response; not even from Paul Squires. I have to question whether I should bother doing that in the future - I probably won't.
OK, I will buy into that slightly. I say slightly because, I reckon, that there are far more existing FB members using WinFBE than there are new users to FB. That is like, nearly, an insurance company or bank giving new customers a cash reward for becoming a new customer but sod all to their loyal customers who may have been with them many years. So, those existing WinFBE users on 2.1.7 and 2.1.8 who were pleased to see gcc 8.4 been used without them having to do anything instead of 5.2, in WinFBE 2.19 and above, which should have been relegated to a museum a long time ago.PaulSquires wrote:This is primarily for consistency for new users to FB so that when they use WinFBE then they'll know that the compiler package backend is based on the official FB distribution.
As does 8.3 ES, 9.3 WL, and 10.2 WL on 1.07.3 where 32-bit is 1.07.2 and 64-bit is 1.07.3codeJeff wrote:Seems to work for the -dll -O2 problem in this topic.
I am surprised that you don't miss more with what you have on your plate.Sorry, I missed your download package.
Don't forget they are my German friend's builds - Mr Anonymous. He writes the books, I just carefully wrap them up and put them into a jiffy bag and post them here.Anyway, looks pretty good. Worth someone testing it. Good job.
Yeah, right. Most members here are more than happy to grab a finished product but get their hands dirty first - no chance.Worth someone testing it.
In which case we should see the 1.07 branch in the rearview mirror shortly.srvaldez wrote:tested the FB gcc-8.3 for wildcard expansion and it works OK
Code: Select all
dim as string x(1 to 4)
x(1) = chr(5,5)
Sleep
I didn't / won't forget. I just don't know what to do with these builds. If there are any issues with the package I guess you will need to respond to the reports as there is nothing I can do to address it. Unless a bug is reported and pushed back on the compiler development (hopefully recorded on github or sourceforge).deltarho[1859] wrote:Don't forget they are my German friend's builds - Mr Anonymous. He writes the books, I just carefully wrap them up and put them into a jiffy bag and post them here.