Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: sergioferrari52 on July 14, 2018, 06:09:36 pm

Title: Code::Blocks next release. Which MinGW/GCC version?
Post by: sergioferrari52 on July 14, 2018, 06:09:36 pm
Wich MinGW/GCC version the Code::Blocks team has planned to distribute in bundle with the next CB release?
Title: Re: Code::Blocks next release. Which MinGW/GCC version?
Post by: oBFusCATed on July 15, 2018, 09:31:22 pm
There isn't a decision made, yet.
Why do you ask?
Title: Re: Code::Blocks next release. Which MinGW/GCC version?
Post by: sergioferrari52 on July 16, 2018, 01:05:16 am
Because I love C++, I love Code::Blocks, I love MinGW and GCC and I would like to have the most updated version of compilers.
Furthermore, it seems that the TDM-GCC project has been abandoned (looking at the website)
However, even CB 17.12 with GCC 5.1.0 is a great IDE / compiler and it helps us a lot to work.
The nightlie GUI is beautiful.
Congratulations to the whole team.
Title: Re: Code::Blocks next release. Which MinGW/GCC version?
Post by: oBFusCATed on July 16, 2018, 08:05:50 am
But our choice doesn't stop you from using another compiler.  ::)
Title: Re: Code::Blocks next release. Which MinGW/GCC version?
Post by: sergioferrari52 on July 16, 2018, 08:33:15 am
Of course!
Title: Re: Code::Blocks next release. Which MinGW/GCC version?
Post by: ouch on July 19, 2018, 06:52:00 am
I've been using Mingw64-i686-8.1.0-posix-sjlj-rt_v6-rev0

It's been working quite well without too many problems for me if you want to try out MingW64.
Title: Re: Code::Blocks next release. Which MinGW/GCC version?
Post by: gd_on on July 19, 2018, 09:53:46 am
Are you sure of the name Mingw64-i686-8.1.0-posix-sjlj-rt_v6-rev0 ?
For me, i686-8.1.0-posix-sjlj-rt_v6-rev0 on sourceforge is a 32 bits only compiler. The 64/32 bits versions are x86_64_8.1.0... files.
Then, which one of the differents "flavour" (as said by TDM) is the best for each/which application ? win32/posix thread ? exceptions sjlj/dwarf for 32 bits, seh/sjlj for 64/32 bits ? Not very clear for me ...

already asked here (http://forums.codeblocks.org/index.php/topic,22354.msg154335.html#msg154335) , but apparently lost in the depths of forums  :-\ !

gd_on
Title: Re: Code::Blocks next release. Which MinGW/GCC version?
Post by: oBFusCATed on July 19, 2018, 10:20:30 am
MingW64 is the project name. Apparently they provide 32 bit compilers, too.

About which version to use: No idea. I don't understand why they provide some many options and make things so confusing.
Title: Re: Code::Blocks next release. Which MinGW/GCC version?
Post by: ouch on July 29, 2018, 07:19:45 am
Yeah I mainly use the 32 bit only version.

Years ago when I tried mingw64 I used the 64 bit version and then added the option to force it into 32 bit mode when I wanted 32 bits. But I found that for whatever reason when you force it into 32bit mode you would occasionally get odd compiler issues. For instance having optimizations on would crash the program. If I then took and used the 32bit version those same optimizations would work fine.

So now days I have both compilers installed, one for 32bit and one for 64bit. Both of these are added to my path variable. I just go into where they are installed and add a "-" in front of whichever one I don't want to use.

For win32 or posix threads: the wxThreads that wxWidgets uses is based on posix style threads so I have always use posix threads myself.

sjlj or dwarf: For all the hype around dwarf about how much better it is than sjlj not many dev tools seem to actually support it very well, or at all. So I pick sjlj. I don't use 64bit version compilers much so I don't know about seh. sjlj has been around for decades though, so I still use sjlj for that.
Title: Re: Code::Blocks next release. Which MinGW/GCC version?
Post by: MortenMacFly on August 19, 2018, 07:40:28 am
I've been using Mingw64-i686-8.1.0-posix-sjlj-rt_v6-rev0
I am using this build for a while now myself (the "gcc.exe (i686-posix-dwarf-rev0, Built by MinGW-W64 project) 8.1.0" from nixman). Could happen that this might be used.

 am using DWARF intentionally for testing...