R:\wxWidgets-3.2.1\include\wx\platform.h|159|fatal error: wx/setup.h: No such file or directory|
||=== Build failed: 4 error(s), 0 warning(s) (0 minute(s), 5 second(s)) ===|
Am I right in thinking that I need to install a copy of wxWidgets that matches one listed in the codeblocks ide?
Are you using the built-in wxWidgets project template wizard? The one shipped with C::B v20.03 does not support wxWidgets v3.2.
You need to use the wizard bundled with the C::B nightly build or the one I provide with my guide (https://github.com/PBfordev/wxpbguide).
Anyway, adding wxWidgets to a project is really simple and no different from any other compiled library. The only difference is that one needs to add two include paths (build-specific and general), but this is well-documented.
Are you suggesting that I am more likely to succeed if I get a recent nightly builds, of codeblocks, (any one, or the most recent?) and there is an included wizard that will install wxWidgetsi.
I've little idea on how to proceed, at the moment. There seems to be too many choices for me, in particular when I have little idea of exactly what I now have on my system.Building wxWidgets is no rocket science, all you need is:
Am I right in thinking that none of this needs to be installed on drive C:, provided i put in the full path name when asked in the installation procedures?
pacman -Syuu
Before you use a nightly make sure you understand how it works.I have no idea on how to install that, so is there an 'idiot's guide' somewhere?
A link to the unicode windows wxWidget dll(s) for Code::Blocks : https://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw32u_gcc_cb_wx321_2D_gcc810-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls8.1.0.7z
The 10 December 2022 build is out.
- Windows :
http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2022/CB_20221210_rev13107_win64.7z
Hi ,
Going through your comprehensive PB guide, I'm stuck. It seems that the page you linked to Para 3.2, , my w10 complains about the fileo says it's unconfirmed, but I tried another page, and got msys2 installed, it needed no updates.
The links to mingw toolchain, no longer seems to exist in para 3.3 . Of course, it could be me, I tried msys2 a week or two back, got nowhere with it. I guess your para 3.4 will be the way to go.
pacman -S mingw-w64-x86_64-toolchain
At least, afasi can tell, I've got wxwin environment variable set up, but then got stuck in trying to do a staticbuild of wx widgets, using your build-library-static.bat. So, as I think you mentioned to use a nightly build of codeblocks,, I thought I 'd try that but it says on that page
ll the 20.03 release, that has a setup, is that the way, then install the nightly?
C:\Users\Ray>cd /d %WXWIN%\build\MSW
R:\wxWidgets-3.2.1\build\msw>mingw32-make -f makefile.gcc SHARED=1 BUILD=debug SHELL=cmd.exe
'mingw32-make' is not recognized as an internal or external command,
operable program or batch file.
R:\wxWidgets-3.2.1\build\msw>R:\msys64\mingw64\bin\mingw32-make -f makefile.gcc SHARED=1 BUILD=release SHELL=cmd.exe
if not exist gcc_mswudll mkdir gcc_mswudll
if not exist ..\..\lib\gcc_dll mkdir ..\..\lib\gcc_dll
if not exist ..\..\lib\gcc_dll\mswu mkdir ..\..\lib\gcc_dll\mswu
if not exist ..\..\lib\gcc_dll\mswu\wx mkdir ..\..\lib\gcc_dll\mswu\wx
if not exist ..\..\lib\gcc_dll\mswu\wx\setup.h copy ..\..\include\wx\msw\setup.h ..\..\lib\gcc_dll\mswu\wx\setup.h
1 file(s) copied.
if not exist ..\..\lib\gcc_dll\mswu\wx\msw mkdir ..\..\lib\gcc_dll\mswu\wx\msw
gcc -E "..\..\include\wx\msw\genrcdefs.h" > "..\..\lib\gcc_dll\mswu\wx\msw\rcdefs.h"
'gcc' is not recognized as an internal or external command,
operable program or batch file.
mingw32-make: *** [makefile.gcc:5987: ..\..\lib\gcc_dll\mswu\wx\msw\rcdefs.h] Error 1
R:\wxWidgets-3.2.1\build\msw>R:\msys64\mingw64\bin\mingw32-make -f R:\wxWidgets-3.2.1\build\msw\makefile.gcc SHARED=1 BUILD=release SHELL=cmd.exe
gcc -c -o gcc_mswudll\wxregex_pcre2_auto_possess.o -O2 -mthreads -DNDEBUG -I..\..\include -I..\..\lib\gcc_dll\mswu -I..\..\3rdparty\pcre\src\wx -D__WX__ -DHAVE_CONFIG_H -D_UNICODE -MTgcc_mswudll\wxregex_pcre2_auto_possess.o -MFgcc_mswudll\wxregex_pcre2_auto_possess.o.d -MD -MP ../../3rdparty/pcre/src/pcre2_auto_possess.c
'gcc' is not recognized as an internal or external command,
operable program or batch file.
mingw32-make: *** [R:\wxWidgets-3.2.1\build\msw\makefile.gcc:6032: gcc_mswudll\wxregex_pcre2_auto_possess.o] Error 1
R:\wxWidgets-3.2.1\build\msw>
R:\wxWidgets-3.2.1\build\msw>set wxwin
WXWIN=R:\wxWidgets-3.2.1
You should, at least add R:\msys64\mingw64\bin to your PATH system variable.Which is, of course, described in my guide and done in the provided build batch files.
R:\wxWidgets-3.2.1\build\msw>set path=r:\mysys64\mingw64\bin%path%
R:\wxWidgets-3.2.1\build\msw>
R:\wxWidgets-3.2.1\build\msw>R:\msys64\mingw64\bin\mingw32-make -f R:\wxWidgets-3.2.1\build\msw\makefile.gcc SHARED=1 BUILD=release SHELL=cmd.exe
gcc -c -o gcc_mswudll\wxregex_pcre2_auto_possess.o -O2 -mthreads -DNDEBUG -I..\..\include -I..\..\lib\gcc_dll\mswu -I..\..\3rdparty\pcre\src\wx -D__WX__ -DHAVE_CONFIG_H -D_UNICODE -MTgcc_mswudll\wxregex_pcre2_auto_possess.o -MFgcc_mswudll\wxregex_pcre2_auto_possess.o.d -MD -MP ../../3rdparty/pcre/src/pcre2_auto_possess.c
'gcc' is not recognized as an internal or external command,
operable program or batch file.
mysys2.exe is in R:\mysys64. I was pretty sure I set the path, but just done it again, with same result.Are you sure your default PATH starts with a semicolon? If not, then the command above does NOT set the correct path to GCC (i.e., you are missing a semicolon between "bin" and "%path%").QuoteR:\wxWidgets-3.2.1\build\msw>set path=r:\mysys64\mingw64\bin%path%
Anyway, I have now run your build -library-shared.bat, however i was disappointed that after possibly an hour of build, it merely finished.Had you followed the advice I gave in the guide and even repeated here (i.e., use the parallel build), it should have taken much less time.
Misleadingly, that window closed, leaving my previous one with the error messages showing...)I do not see what is misleading about the window with successful build closing, as described in the guide and the batch file, the window is left open only when the build fails, so the build error messages remain available.
I want to install the static build version, if that can coexist with the debug/release versions. Do I just delete the two folders you mention in cleaning the gcc builds, and run the static build batch file?You are mixing two things here, static/shared (affected by the value of the build parameter "SHARED") and debug/release (affected by the value of the build parameter "BUILD"). They are used together, you cannot have one without other, e.g. you can have a static debug build, a shared release build, and/or any other of the four possible combinations. They do not affect each other. As described in the guide, the libraries for the debug build have an extra "d" in their name so they can coexist in the same folder with the release libraries. Also as described there, static builds are by default generated in "WXDIR/lib/gcc_lib" while the shared ones in "WXDIR/lib/gcc_dll".