User forums > General (but related to Code::Blocks)

wxWidgets 3.0.3 released

(1/7) > >>

stahta01:
Since wxWidgets 3.0.3 released; I am going to once more try to fix the CB Projects and Wizards to use the wxTeam prebuilt binaries. Maybe this time, I will finish it and have a CB Dev like the way I do at least part of the work.

https://github.com/wxWidgets/wxWidgets/releases/tag/v3.0.3

Tim S.

killerbot:
Yesterday I have tried to build CB with it : mixed results.

Environment :
- Win 10 (64 bit)
- TDM-gcc 5.1.0 ==> which creates by default 64 bit targets (I used it like that)

I build wx like I used to build the 2.8.12, that is like described on the nightly cookbook. ==> no problems

--- Quote ---I did NOT specify -std=c++11 !!!!
--- End quote ---
(need to investigate if this is not the default gcc 5.1, otherwise my build of wx is not correct)

Then I build CB by using the wx30_64 workspace.

--- Quote ---The project files of the wx30_64 explicitly specify -std=c++11
--- End quote ---

The build failed because the fortran plug-in does not compile, it needs in parserf.cpp to include <wx/regex.h>.

The I can launch the freshly build CB, it comes up nicely, but without any interaction a few seconds later it crashes.

stahta01:
Edit4: Deleted wxWidgets message that went away after I deleted the MSys2 GCC 6.3.0 DLLs.

The MinGW32 GCC TDM 5.1.0 gets the above message using the wxTeam built binary with edited project.
Now, it looks like I need to build wxWidgets using my "MinGW32 GCC TDM 5.1.0" to see if the error was caused by a compiler version/build type issue.

Edit: It never really displays the CB IDE before it crashes.
Edit3: It stopped crashing after I deleted the DLLs left over from the MSys2 GCC 6.3.0 testing.
Edit2: Testing on Windows 10 32 bit.

NOTE: The wxTeam used the flags below to build their GCC 510TDM binary

--- Code: ---CXXFLAGS=-fno-keep-inline-dllexport -std=gnu++11

--- End code ---

Tim S.

killerbot:
as for gcc, I think the default mode in 5.x is not "c++11", in 6.x it became "The default mode for C++ is now -std=gnu++14 instead of -std=gnu++98".

So I think indeed when we build wx with the 5.x we should clearly specify the standard we want to use.
I think it is best to stick to official standard and not gnu extension ==> -std=c++11

So when mixing what you saw from wxTeam (no idea what wxTeam is ) and our cookbook we should get something like:


--- Code: ---CXXFLAGS+=-fpermissive -fno-keep-inline-dllexport -std=c++11

--- End code ---

Need to see what the correct syntax is to end up with the following invocation for building wx :


--- Code: ---mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 vendor=CB CXXFLAGS+=-fpermissive -fno-keep-inline-dllexport -std=gnu++11

--- End code ---

should it it be CXXFLAGS+="blablablablabla ablablalb "  ?

stahta01:
This is the syntax I think it should use.


--- Code: ---CXXFLAGS="-fpermissive -fno-keep-inline-dllexport -std=gnu++11"

--- End code ---

Full command below:

--- Code: ---mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 vendor=CB CXXFLAGS="-fpermissive -fno-keep-inline-dllexport -std=gnu++11"

--- End code ---

Edit: I am using wxTeam in place of the wxWidgets development team; in this exact case I mean the sub-set of people who created the wxWidgets multilib binaries I am using.

Navigation

[0] Message Index

[#] Next page