User forums > General (but related to Code::Blocks)
wxWidgets 3.0.3 released
icequan233:
Another quesition: the codeblocks editor has some problem on hidpi, http://forums.codeblocks.org/index.php/topic,21789.0.html ,It seems our editor don't support hidpi,
the wxscintilla implement with scintilla based on wxWidgets, but the latest version of scintilla is imcompatible with our version(3.5.3), too many code need be updated in cb. but the wxstyledtextctrl
almost same with wxscintilla(???), Is it possible use wxstyledtextctrl? or has anyone update the code of wxscintilla? Thanks.
oBFusCATed:
--- Quote from: icequan233 on May 08, 2017, 07:08:10 am ---Is it possible use wxstyledtextctrl? or has anyone update the code of wxscintilla?
--- End quote ---
No and no, but I plan to try soon.
gd_on:
Hi,
I tried to build CB with wxwidgets 3.0.3 and 3.1, but in 32 bits. Same problem : CB crash a few second after starts and almost same crash report as mentionned by killerbot.
In my case, I compile with TDM 4.9.2 version (I don't use 5.1 version, because of a bugged gfortran and I prefer to have only one set of compilers for my standard work !).
I also tried some newer windows gnu compilers (officials MinGW 6.2, 6.3 or 7.1, found on https://sourceforge.net/projects/mingw-w64/files/?source=navbar)
With 6.2, same CB problem, same crash.
With 6.3 and 7.1, there is already a problem in wxwidgets compilation (at link time), so no way to build CB (a double definition inside libuuid.a, strange !).
More, I have a question probably out of this topic :
I seems that TDM versions are more or less abandoned (I'm not sure, but I think so).
Have you (CB developpers) plans for MinGW compilers recommandations on Windows : which version, win32/posix, sjlj/dwarf/seh ...
For my tests, I tried posix-sjlj for 32 bits versions, and posix-seh for 64 bits versions, but I'm not sure it's the good (or best) choice.
I also tested with win32-sjlj but this makes no difference concerning CB crash or wxwidgets link error as far as I can see.
gd_on
stahta01:
--- Quote from: gd_on on May 22, 2017, 11:28:52 am ---With 6.3 and 7.1, there is already a problem in wxwidgets compilation (at link time), so no way to build CB (a double definition inside libuuid.a, strange !).
--- End quote ---
I traced the likely caused of the linking error of the Monolithic wxwidgets shared/DLL build to the MinGW64 C Runtime Library.
(I forget if I saw the issue with Monolithic wxwidgets static build; I really think that build makes no sense; and, rarely test it.)
I have yet to post in the MinGW64 mail/newsgroup to find out how to submit the fix and what type of fix the MinGW64 people would want. If you are using MSys2, I created a patch to fix the issue under it.
Edit: I read about a work around on the issue today; I will try to find it.
From https://github.com/Alexpux/MINGW-packages/issues/1761
--- Quote ---I have found a workaround. Just pass the --allow-multiple-definition option to ld (use the -Wl, gcc option for that).
--- End quote ---
Not had time to test that work around.
Tim S.
gd_on:
With the suggested "workaround", it's better to build wxwidgets 3.1 with MinGW 7.1.
I added LDFLAGS="-Wl,--allow-multiple-definition" on the make line.
Neverthess, when I try to build the samples tests cases, it compiles, but crashes when I launch executables ! :-[
And I "only" use Msys 1, so the patch may be not relevant.
And finally, no success to build CB until now : some incompatibilities in libwxmsw31u.a. I have added the -Wl,--allow-multiple-definition in linker option, but it's not sufficient.
I have to search more to find what's wrong.
gd_on
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version