Talk:CodeBlocks Setup Guide
The descripted install procedure for 2.6 library is a little bit outdated. Here is a newer description: http://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.8.6_to_develop_Code::Blocks_(MSW)
Magnus 19:11, 5 September 2008 (UTC)
The following deviations were noted when
with a setup of current mingw and wxWidgets-2.6.3
for use with CodeBlocks on Windows OS
In making the wxWidgets libraries :-
Ensure the PATH environment variable has the Mingw\bin directory.
The make command was mingw32-make.
Some build configurations co-exist in the same directory, eg debug and release builds in $(WXWIN)\lib\gcc_dll
USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=debug UNICODE=0
USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0
The debug libraries have a 'd' on the end of the name.
Seperate configuration and build directories are created.
Configuration :- include the right one in codeblocks compiler configuration
$(WXWIN)\lib\gcc_dll\msw
$(WXWIN)\lib\gcc_dll\mswd
So haven't needed to rename folders
I noticed that my PC was only taking up 50% CPU when compiling. I added in the -j2 option to the make use of both processors on my PC.
as.exe - entry point not found
After editting my config.gcc to specify the correct options, I tried to execute
mingw32-make.exe -f makefile.gcc
Then I got the following error:
The procedure entry point __printf__ could not be located in the dynamic link library "c:\Program Files (x86)\CodeBlocks\MinGW\bin..\lib\gcc\mingw32\5.1.0\..\..\..\..\mingw32\bin\as.exe"
On stackoverflow.com I found that this can be prevented by renaming the folder c:\Program Files (x86)\CodeBlocks\MinGW\mingw32 to mingw32old. Prior to this I attempted to execute c:\Program Files (x86)\CodeBlocks\MinGW\mingw32\bin\as.exe which resulted in the same error.
I'm not sure why this happens, but unless a better solution is available, I think it should be noted in the setup guide.