Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Patches for Compiling Code::Blocks against wxWidgets 3.0 using MinGW GCC 4.8.1
stahta01:
--- Quote from: oBFusCATed on November 13, 2013, 10:08:07 pm ---
--- Quote from: stahta01 on November 13, 2013, 04:25:14 pm ---Do you think the wx/gauge.h should be included in sdk_common.h?
--- End quote ---
I don't know, what difference does it make?
--- End quote ---
If you use PCH correctly you need to fix the code so it compiles.
My patches work; if you wish to speed up compiling including a header only used once in the PCH wastes time and memory.
But, right now we are including all the headers inside wx/prec.h inside the SDK.h PCH.
Tim S.
stahta01:
--- Quote from: killerbot on November 13, 2013, 09:34:12 pm ---suggestion : let us just stop using PCH's.
Compiling CB goes rather quickly (even without using pch's) and when one can use multi cores it goes amazingly fast.
Time after time, this is biting us. Let's try without and see where we end up ?
--- End quote ---
I could try that route; I am nearly positive the 4.8.1 crash will go away.
Building of the Code::Blocks core project will likely be slower.
But, since the contrib projects already do NOT use the PCH version of sdk.h they should be no slower.
And, removing the flags doing precomp should speed up the building of the Contrib projects.
Will see if this solution works for 4.8.1 and see if it speeds up building CB Core project after I turn off the precomp flags.
Tim S.
ollydbg:
FYI:
Hi, Tim and other guys, I just update a GCC bug:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
I can reproduce the bug with a very simple test code (only MinGW compiler suite and boost header files are needed), so it looks like GCC can not read/handle big PCH files. See this Comment 6 with steps.
ollydbg:
Nowadays, I'm trying to find the reason why the big pch will cause gcc crash. Now, I see that I may find the reason, the hard limited pch file size is around 128M, see my post in mingw-w64 forum for the information. [Mingw-w64-public] Set a larger pch file size limit? was : can anyone supply a debug version of cc1plus.exe?
Any one can build a new gcc tool chain which has larger hard coded value?
stahta01:
--- Quote from: ollydbg on May 31, 2015, 10:27:08 am ---Nowadays, I'm trying to find the reason why the big pch will cause gcc crash. Now, I see that I may find the reason, the hard limited pch file size is around 128M, see my post in mingw-w64 forum for the information. [Mingw-w64-public] Set a larger pch file size limit? was : can anyone supply a debug version of cc1plus.exe?
Any one can build a new gcc tool chain which has larger hard coded value?
--- End quote ---
I have given up on finding the PCH build size issue cause.
But, I am now trying to cross build Code::Blocks under Debian Jessie using MinGW64 gcc for 32 bit build.
If I can duplicate the error under Debian Jessie, would that help you find the PCH bug?
Tim S.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version