Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
to which compiler should we step up to bundle with CB
killerbot:
didn't know that one existed, cool, but seems outdated.
PCH problems, hmm, as my track record in this forum shows, I hate them, they are nothing but troubles ;-)
killerbot:
I have successfully build with this "https://github.com/brechtsanders/winlibs_mingw/releases/download/13.1.0-16.0.2-11.0.0-ucrt-r1/winlibs-x86_64-mcf-seh-gcc-13.1.0-llvm-16.0.2-mingw-w64ucrt-11.0.0-r1.zip"
* wxwidgets 3.2.2.1
* CB trunk
First runs seem to be ok.
I think this is a compiler bundle worth using ...
Maybe as the base for the next nightly ... ?
ollydbg:
--- Quote from: killerbot on May 20, 2023, 03:37:10 pm ---I have successfully build with this "https://github.com/brechtsanders/winlibs_mingw/releases/download/13.1.0-16.0.2-11.0.0-ucrt-r1/winlibs-x86_64-mcf-seh-gcc-13.1.0-llvm-16.0.2-mingw-w64ucrt-11.0.0-r1.zip"
* wxwidgets 3.2.2.1
* CB trunk
First runs seem to be ok.
I think this is a compiler bundle worth using ...
Maybe as the base for the next nightly ... ?
--- End quote ---
I'm OK with this gcc suite, although I use msys2's gcc.
Note that I got a notification email that Release GCC 12.3.0 + LLVM 16.0.4 + MinGW-w64 11.0.0 MSVCRT (release 1) brechtsanders/winlibs_mingw released yesterday.
Miguel Gimenez:
@killerbot, that release uses UCRT instead of MSVCRT. This would force users < Windows 10 to install the UCRT as a prerequisite, even for software deployment. Previous release uses MSVCRT.
killerbot:
correct, but I have a feeling we should ditch pre win10 stuff. MSVCRT is suggested not to be used anymore ...
It is worth considering to try this approach out ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version