Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

to which compiler should we step up to bundle with CB

<< < (2/6) > >>

sodev:

--- Quote from: blauzahn on May 09, 2023, 07:23:19 am ---At the moment, wxwidgets trunk does not compile out of the box with gcc-13.1.1.

--- End quote ---

Compiles fine for me on Fedora 38 with gcc 13.1.1.


--- Quote from: killerbot on May 09, 2023, 07:44:18 am ---Personally I am not so fond of msys2, seems to complicated, compared to the more simple compiler bundles we used to ship.

--- End quote ---

The great thing of MSYS2 is, that you can get a lot of libraries easily. However, this setup only works easily if you use its shell, using the compiler standalone is cumbersome. For that use case, it's easier to use a standalone compiler like a plain MinGW-w64. But getting libraries compiled with such a compiler can be very hard. So well, for the "CodeBlocks @school" use case that uses nothing more than std::cout standalone is probably better, but for the Real-World use case MSYS2 might be better.

blauzahn:
@sodev: Indeed. Wxwidgets compiles fine ootb with gcc-13.1.1. I mixed it up with cppcheck where a static_assert fails. Thank you for correcting me.

With gcc-10 I meant the minimum version cb should be able to compile with at the moment. I appreciate bundling a newer gcc with cb on windows (only) so that users can use newer features. Being restricted to a compiler lagging several versions behind might discourage from using it and therefore cb on Windows. This might also frustrate cb-devs. Lets hope that the coming debian version will be available on Pi os soon.

ollydbg:

--- Quote from: sodev on May 09, 2023, 06:10:56 pm ---The great thing of MSYS2 is, that you can get a lot of libraries easily. However, this setup only works easily if you use its shell, using the compiler standalone is cumbersome. For that use case, it's easier to use a standalone compiler like a plain MinGW-w64. But getting libraries compiled with such a compiler can be very hard. So well, for the "CodeBlocks @school" use case that uses nothing more than std::cout standalone is probably better, but for the Real-World use case MSYS2 might be better.

--- End quote ---

I think most package supplied by MSYS2 can by used by pkg-config command from a normal Windows CMD.
For example, below code is from one of my Code::Blocks project's linker options. I link to glm, glfw3, glew and wx libraries supplied by MSYS2. The last line is actually using wx-config-msys2.exe.

--- Code: ---`pkg-config --libs glm`
`pkg-config --libs glfw3`
`pkg-config --libs glew`
`$(#WX_CONFIG) --libs all`

--- End code ---

I think its simple and powerful to use MSYS2.

killerbot:
anyone any epxerience with this one, looks very promising : https://winlibs.com/ (I choose the one without clang), and the content of it is (a bot to much maybe (cmake / ninja/ ..):

This is the winlibs 64-bit standalone build of:
- GCC 13.1.0
- GDB 13.1
- MinGW-w64 11.0.0 (linked with ucrt)
- GNU Binutils 2.40
- GNU Make 4.4.1
- PExports 0.47
- dos2unix 7.4.4
- Yasm 1.3.0
- NASM 2.16.01
- JWasm 2.12pre
- ccache version 4.8
- CMake 3.26.3
- ninja 1.11.1
- doxygen 1.9.6

Miguel Gimenez:
I have checked the Nuwen distro from Stephen T. Lavavej, it includes GCC 11.2.0 and Boost 1.77, and works fine except for two annoyances:

- The included binutils has a linking bug that can be solved deleting a flie from the distro
- C::B does not compile due to PCH problems (lot of errors from MapViewFileEx). I do not know if this is a problem from the distro or from GCC 11.2

Navigation

[0] Message Index

[#] Next page

[*] Previous page