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

CB Compile time

<< < (2/2)

dominover:
I just installed the same version of CB with MinGW 4.71 as well and wxWidgets takes forever initially.
Will be interested to hear what the final solution is on that.

thomas:

--- Quote from: comsytec on February 13, 2013, 08:47:17 am ---Have you fallen into trouble linking wxWidgets due to exhausted memory ? This happens to me with TDM-GCC 4.7.1 but not with GCC 3.4.5. I know this to forum about wxWidgets but it is used for the CB so I ask.

--- End quote ---
Under a 32bit system, with LTO enabled, yes, that will happen (LTO eats up about 2.7 GiB of working set for that task). It just barely works if you patch the ld executable to have the LARGEADDRESSAWARE flag set and reboot with /3G. Or well, if you use 64 bits of course, you don't have any trouble.

Without enabling LTO, you shouldn't have any such issues, ever -- unless you run on an embarrassingly low spec machine with too little physical RAM. I've been building wxWidgets on machines with 1GiB of main memory no problem.

comsytec:
We used

--- Code: ---mingw32-make.exe -f makefile.gcc VENDOR=cb BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1

--- End code ---
to build wxWidgets which took I dont know exactly 30-40 mins on dual core XP machine 2.4GHz machine without antivirus scanner but always failes on the link step. To solve link troubles we have used the bash script above. Of course you need customize it with your own Mingw paths.

Jenna:

--- Quote from: oBFusCATed on February 13, 2013, 09:07:58 am ---Search the forum, I think this is discussed in other topics (probably the TDM topics).
I think you need monolithic or non-monolitic builds (depends on what you're currently using, you need the opposite config)

--- End quote ---

--- Quote from: comsytec on February 13, 2013, 08:47:17 am ---Have you fallen into trouble linking wxWidgets due to exhausted memory ? This happens to me with TDM-GCC 4.7.1 but not with GCC 3.4.5. I know this to forum about wxWidgets but it is used for the CB so I ask.

--- End quote ---
Adding CXXFLAGS="-fno-keep-inline-dllexport" to the make commandline should fix the exhausted memory issue.

Navigation

[0] Message Index

[*] Previous page