User forums > Using Code::Blocks
Upgrading to wxWidgets 3.1.3
stahta01:
--- Quote ---For use in debug mode is a separate debug compilation of wxWidgets 3.1.3 required?
--- End quote ---
No, but sometimes you might wish to make one with all the symbols.
The wxWidgets in 3.1 is normally build with debug symbols; but, it can be built with more or less debug information. wxWidgets 2.8 was normally built without debug information. Not sure about 3.0
Tim S.
spflanze:
Thanks for your reply. I made all those global file fields blanks as you recommended. That path is now a valid one. I made a bad assumption when I thought the content of those fields would be appended to the base. I see now they are not, and are a complete replacement for what is default.
The project still does not compile. In the error message I see: -Winvalid-pch. I think this is a message from the make file that says something has gone wrong with precompiled headers. Your suggestions about troubleshooting this would be appreciated.
This is the command I used to compile wxWidgets.
--- Code: ---mingw32-make -f makefile.gcc SHARED=1 UNICODE=1 BUILD=release
--- End code ---
It is copied from this web page: https://wiki.wxwidgets.org/Compiling_wxWidgets_with_MinGW
If I were to compile for those higher levels of debug ability, how would this be changed?
stahta01:
Post the current build log?
And, are you wanting to build an wxWidgets shared/DLL or a static library?
Because, what you have posted conflicts with each other.
Edit from build/msw/config.gcc
--- Code: ---# Type of compiled binaries [debug,release]
BUILD ?= debug
# Should debugging info be included in the executables? The default value
# "default" means that debug info will be included if BUILD=debug
# and not included if BUILD=release. [0,1,default]
DEBUG_INFO ?= default
# Value of wxDEBUG_LEVEL. The default value is the same as 1 and means that all
# but expensive assert checks are enabled, use 0 to completely remove debugging
# code. [0,1,default]
DEBUG_FLAG ?= 1
--- End code ---
Edit2: To have the most debug information I think you need to use "DEBUG_FLAG=2" when building wxWidgets.
Edit3: See wx/debug.h for more information
Tim S.
sodev:
--- Quote from: spflanze on February 21, 2020, 02:00:47 am ---That is where 3.1.2 was. I missed that earlier. Thanks. Now I am seeking to use the wx variable to make future upgrades easier. In the path: "Settings => Global variables => wx" I have these settings:
--- Code: ---base: C:\wxWidgets-3.1.3
include:
lib: \lib\gcc_lib
bin: \bin
--- End code ---
--- End quote ---
These leading backslash in the lib and bin path might be interpreted as absolute path and this seems to result into this path beeing used as-is. Without the leading backslash for me these fragments get correctly appended to the base path. If the fields are empty they expand into their name. The CodeBlocks project files append the gcc_lib fragment themself (which is kind if annoying for me because my wxWidgets builds use tagged output folders for quite some time now.
--- Quote ----Winvalid-pch
--- End quote ---
This is not an error message but a compiler option to enable a warning about incompatible PCH settings, this won't create a compiler error.
--- Quote ---mingw32-make -f makefile.gcc SHARED=1 UNICODE=1 BUILD=release
--- End quote ---
You are building on windows and AFAIK the CodeBlocks project files require a monolithic build, this might be the cause for your errors. Add a MONOLITHIC=1 and check if this resolves your errors.
stahta01:
--- Quote from: sodev on February 21, 2020, 06:19:13 pm ---You are building on windows and AFAIK the CodeBlocks project files require a monolithic build, this might be the cause for your errors. Add a MONOLITHIC=1 and check if this resolves your errors.
--- End quote ---
False, the CB projects to build CB require MONOLITHIC; but, there is no issues using an non MONOLITHIC project in CB.
Tim S.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version