Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
CodeBlocks includes for wxWidgsts
stahta01:
Link to a patches I am working on for the CB wxWidgets wizard https://sourceforge.net/p/codeblocks/tickets/508/
Note: I still do not understand why you think there is a problem building Code::Blocks that the project needs patched.
I agree the order you suggest is better; but, unless you manually copied an setup.h under the wx folder you should not normally get a build problem.
If you have a real problem building Code::Blocks post your build log with the problem.
Tim S.
Uskok:
--- Quote from: stahta01 on January 12, 2018, 07:27:06 am ---Why do you think the header "wx/msw/setup.h" will be used instead of "wx/setup.h"?
I do think changing the order of search paths is a good idea; but, I do not see your logic as valid.
I would change it because I am guessing it would be a tiny bit faster building; but, I have never really seen any build speed improvements when I first tried it several years ago. But, my hardware is old and its speed various a lot on each build test.
Tim S.
--- End quote ---
You are right. I putted wrong path. The correct is as you wrote ..\lib\gcc_dll\mswu\wx\setup.h
Wrong copy paste.
It is not the question of speed up the compilation time, it is the usage of the wrong header file. The nice trick what is done in wxWidgets is to tune your own copy of the setup.h and it is dedicated to the build. You can have N parallel build under lib folder, different compiler and version with different options.
Uskok:
--- Quote from: stahta01 on January 12, 2018, 07:42:44 am ---Link to a patches I am working on for the CB wxWidgets wizard https://sourceforge.net/p/codeblocks/tickets/508/
Note: I still do not understand why you think there is a problem building Code::Blocks that the project needs patched.
I agree the order you suggest is better; but, unless you manually copied an setup.h under the wx folder you should not normally get a build problem.
If you have a real problem building Code::Blocks post your build log with the problem.
Tim S.
--- End quote ---
Hi Tim,
Take a look on the build process:
D:\Dev\MinGW-TDM-510-x64>mingwvars.bat
Setting up environment for using MinGW with GCC from D:\Dev\MinGW-TDM-510-x64\.
D:\Dev\MinGW-TDM-510-x64>cd D:\Dev\wxWidgets-3.0.3\build\msw
D:\Dev\wxWidgets-3.0.3\build\msw>mingw32-make -f makefile.gcc
if not exist gcc_mswud mkdir gcc_mswud
if not exist ..\..\lib\gcc_lib mkdir ..\..\lib\gcc_lib
if not exist ..\..\lib\gcc_lib\mswud mkdir ..\..\lib\gcc_lib\mswud
if not exist ..\..\lib\gcc_lib\mswud\wx mkdir ..\..\lib\gcc_lib\mswud\wx
if not exist ..\..\lib\gcc_lib\mswud\wx\setup.h copy ..\..\include\wx\msw\setup.h ..\..\lib\gcc_lib\mswud\wx\setup.h
1 file(s) copied.
if not exist ..\..\lib\gcc_lib\mswud\wx\msw mkdir ..\..\lib\gcc_lib\mswud\wx\msw
gcc -E "..\..\include\wx\msw\genrcdefs.h" > "..\..\lib\gcc_lib\mswud\wx\msw\rcdefs.h"
gcc -c -o gcc_mswud\wxregex_regcomp.o -g -O0 -mthreads -DHAVE_W32API_H -DNDEBUG -I..\..\include -I..\..\lib\gcc_lib\mswud -D__WXMSW__ -D_U
NICODE -MTgcc_mswud\wxregex_regcomp.o -MFgcc_mswud\wxregex_regcomp.o.d -MD -MP ../../src/regex/regcomp.c
gcc -c -o gcc_mswud\wxregex_regexec.o -g -O0 -mthreads -DHAVE_W32API_H -DNDEBUG -I..\..\include -I..\..\lib\gcc_lib\mswud -D__WXMSW__ -D_U
NICODE -MTgcc_mswud\wxregex_regexec.o -MFgcc_mswud\wxregex_regexec.o.d -MD -MP ../../src/regex/regexec.c
gcc -c -o gcc_mswud\wxregex_regerror.o -g -O0 -mthreads -DHAVE_W32API_H -DNDEBUG -I..\..\include -I..\..\lib\gcc_lib\mswud -D__WXMSW__ -D_
UNICODE -MTgcc_mswud\wxregex_regerror.o -MFgcc_mswud\wxregex_regerror.o.d -MD -MP ../../src/regex/regerror.c
gcc -c -o gcc_mswud\wxregex_regfree.o -g -O0 -mthreads -DHAVE_W32API_H -DNDEBUG -I..\..\include -I..\..\lib\gcc_lib\mswud -D__WXMSW__ -D_U
NICODE -MTgcc_mswud\wxregex_regfree.o -MFgcc_mswud\wxregex_regfree.o.d -MD -MP ../../src/regex/regfree.c
if exist ..\..\lib\gcc_lib\libwxregexud.a del ..\..\lib\gcc_lib\libwxregexud.a
ar rcu ..\..\lib\gcc_lib\libwxregexud.a gcc_mswud\wxregex_regcomp.o gcc_mswud\wxregex_regexec.o gcc_mswud\wxregex_regerror.o gcc_mswud\wxreg
ex_regfree.o
ranlib ..\..\lib\gcc_lib\libwxregexud.a
gcc -c -o gcc_mswud\wxzlib_adler32.o -g -O0 -mthreads -DHAVE_W32API_H -DNDEBUG -MTgcc_mswud\wxzlib_adler32.o -MFgcc_mswud\wxzlib_adler32.
o.d -MD -MP ../../src/zlib/adler32.c
gcc -c -o gcc_mswud\wxzlib_compress.o -g -O0 -mthreads -DHAVE_W32API_H -DNDEBUG -MTgcc_mswud\wxzlib_compress.o -MFgcc_mswud\wxzlib_compre
ss.o.d -MD -MP ../../src/zlib/compress.c
gcc -c -o gcc_mswud\wxzlib_crc32.o -g -O0 -mthreads -DHAVE_W32API_H -DNDEBUG -MTgcc_mswud\wxzlib_crc32.o -MFgcc_mswud\wxzlib_crc32.o.d -M
D -MP ../../src/zlib/crc32.c
makefile.gcc:5720: recipe for target 'gcc_mswud\wxzlib_crc32.o' failed
mingw32-make: *** [gcc_mswud\wxzlib_crc32.o] Error 3
D:\Dev\wxWidgets-3.0.3\build\msw>
The first copy of setup.h is done in make self. wxWidgets developers made nice trick. You will get the master copy, if it is the first run of make.
Then you can change what you like to tune and rebuild the library.
stahta01:
So, are you having a problem building Code::Blocks or not?
Tim S.
Uskok:
--- Quote from: stahta01 on January 12, 2018, 09:40:07 am ---So, are you having a problem building Code::Blocks or not?
Tim S.
--- End quote ---
Of course, as is written in my first entry of the theme. I have done some investigation.
My assumption of the problem was wrong.
..\..\include\wx\msw\setup.h is not used during the build process only ..\..\lib\gcc_lib\mswu(d)\wx\setup.h
That means, the current order of includes can be as it is.
The solution for my problem is to use "-O2 -DNDEBUG" instead "-g" for real release inside cb_release_type. -DNDEBUG removes my problem with build of Code::Blocks.
Thanks for support.
Navigation
[0] Message Index
[*] Previous page
Go to full version