Recent Posts

Pages: 1 2 3 [4] 5 6 7 8 9 10
31
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by stahta01 on February 22, 2020, 06:09:43 am »
What is the CB compiler toolchain path set to?
"Compiler Installation Directory"
Edit2: Settings -> Compiler
Select the correct compiler
Tab: Toolchain Executable


Post the build log; either you are compiling the same file or you are not!

If you are still compiling the old file [wx_pch.h] then you failed to stop compiling it.

Tim S.
32
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by spflanze on February 22, 2020, 05:02:35 am »
I turned off the compilation of the file wx_pch.h. I did this by right clicking on it, and in the pop up menu, unchecking the "Compile file" box at  "Properties => Build (tab"). In that tab the "Link file" checkbox is also unchecked. It still did not compile. It was the same error as before.

The compiler is on the path: C:\Program Files\mingw-w64\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin\ . Here the gcc.exe and g++.exe compilers are used for both compiling wxWidgets, and my application in Code::Blocks. I verified this with the Window 7 command prompt's "where" command. This compiler setup was installed using the file "mingw-w64-install.exe", which was downloaded from https://mingw-w64.org/doku.php. I see now I do not have the latest version of it.

I searched the entire disk drive for the file "mingw32-g++.exe" using the Windows Explorer. I found it in several places, including an embedded development installation. I attempted to find out which of them is executed when I attempt to compile my application in Code::Blocks using the Windows 7 command prompt command "where mingw32-g++.exe". But the where command could not find any instances of it, in spite of the Windows Explorer's search results.
33
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by sodev on February 22, 2020, 01:54:34 am »
Code: [Select]
[  5.0%] mingw32-g++.exe -Wall -pipe -mthreads...

This percentage display at the start of line looks unfamiliar for me, usually the CodeBlocks build system doesn't output that. Are you using CMake or so as build system?
34
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by stahta01 on February 22, 2020, 01:06:33 am »
NOTE: I would stop trying to build the pch file till you get the rest of the files to build.
The error message is not very good while building the PCH (Precompiled Header)

You can do this by disable compile on the file "wx_pch.h"
And, I would remove the option "-include wx_pch.h" till you start trying to build PCH again.
You also, should replace "-DWX_PRECOMP" with "-DNOPCH"

Tim S.
35
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by stahta01 on February 22, 2020, 12:53:55 am »
Please post information about your Compiler?

Edit: You do know that wxWidgets is a C++ Library, therefore you should use the same compiler to built it and the code that uses the library.

And, to build a 64 bit application the compiler and the library both need to be 64 bit.

Tim S.
36
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by spflanze on February 22, 2020, 12:22:30 am »
I recompiled wxWidgets. This is the batch file I did it with:

Code: [Select]
REM Change the current working directory
cd  C:\wxWidgets-3.1.3\build\msw

REM Compile the release version
mingw32-make -f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 BUILD=release clean
mingw32-make -f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 BUILD=release

REM Compile the debug version
mingw32-make -f makefile.gcc MONOLITHIC=1  SHARED=1 UNICODE=1 BUILD=debug clean
mingw32-make -f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 BUILD=debug

In Code::Blocks, when I attempt to compile in debug my application that did compile before the wxWidgets upgrade, I still get an error:
Code: [Select]

-------------- Build: Debug in TIA Designer (compiler: GNU GCC Compiler)---------------

[  5.0%] mingw32-g++.exe -Wall -pipe -mthreads -Winvalid-pch -include wx_pch.h -D__GNUWIN32__ -D__WXMSW__ -DwxUSE_UNICODE -DWX_PRECOMP -g -D__WXDEBUG__ -Winline -Wall -pg -m64 -g -g3 -I..\Libraries\cminpack-1.3.6 -IC:\wxWidgets-3.1.3\lib\gcc_dll\mswud -c "C:\Software\Designer\wx_pch.h" -o "wx_pch.h.gch\Debug_TIA Designer_wx_pch_h_gch"

Execution of 'mingw32-g++.exe -Wall -pipe -mthreads -Winvalid-pch -include wx_pch.h -D__GNUWIN32__ -D__WXMSW__ -DwxUSE_UNICODE -DWX_PRECOMP -g -D__WXDEBUG__ -Winline -Wall -pg -m64 -g -g3 -I..\Libraries\cminpack-1.3.6 -IC:\wxWidgets-3.1.3\lib\gcc_dll\mswud -c "C:\Software\Designer\wx_pch.h" -o "wx_pch.h.gch\Debug_TIA Designer_wx_pch_h_gch"' in 'C:\Software\Designer' failed.
37
Using Code::Blocks / Re: Weird tabs behavior
« Last post by oBFusCATed on February 21, 2020, 08:45:52 pm »
And what is your wxGTK version? (Execute wx-config --list and paste the results from it)
38
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by sodev on February 21, 2020, 07:01:33 pm »
Oops, for some unknown reason i thought he is building CodeBlocks ::) ;D

Well, but because he is not, it is easier to use a debug build of wxWidgets.

Code: [Select]
mingw32-make -f makefile.gcc SHARED=1 UNICODE=1 BUILD=debug
This produces a variant with debug symbols and also enables the assertions. No need to mess around with debug levels, the default settings are good enough. Create a second configuration and link against that debug variant.

About possible PCH related problems, depending on the PCH strategy CodeBlocks might not delete a present PCH file. Check the output folders and remove all PCH files to start a fresh build.
39
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by stahta01 on February 21, 2020, 06:46:14 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.

False, the CB projects to build CB require MONOLITHIC; but, there is no issues using an non MONOLITHIC project in CB.

Tim S.
40
Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3
« Last post by sodev on February 21, 2020, 06:19:13 pm »
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: [Select]
base: C:\wxWidgets-3.1.3
include:
lib: \lib\gcc_lib
bin: \bin

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

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

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.
Pages: 1 2 3 [4] 5 6 7 8 9 10