User forums > Using Code::Blocks
missing wx/setup.h
PB:
--- Quote from: bdad on December 12, 2022, 08:39:02 pm ---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.
--- End quote ---
You should have downloaded and run file msys2-x86_64-20221028.exe. Did you?
--- Quote from: bdad on December 12, 2022, 08:39:02 pm ---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.
--- End quote ---
There are only two links in Chapter 3.3: https://packages.msys2.org/group/mingw-w64-x86_64-toolchain and https://www.msys2.org/docs/environments/#msvcrt-vs-ucrt and they are both working.
More importantly, they are not really needed for installing the compiler or installing wxWidgets, they only provide an optional information.
If you do not install the compiler package properly, you will not be able to continue with building wxWidgets or your application. This means you should start MSYS2 environment, run
--- Code: ---pacman -S mingw-w64-x86_64-toolchain
--- End code ---
and press Enter when asked about installation.
But as I write in the guide, using MSYS2 is not mandatory, any compatible recent(-ish) mingw-64-based GCC distribution should work.
PB:
--- Quote from: bdad on December 12, 2022, 09:57:36 pm ---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?
--- End quote ---
Code::Blocks version and building wxWidgets are utterly unrelated, i.e., C::B version cannot in any way affect wxWidgets build. If you have a build error, you need to take a look at the error message.
You can also just use C::B v20.03 with my updated wizard from the guide GitHub repo, it even has a nice batch file to install it for the current C::B version.
But you seem to have an unusually high number of issues with such a simple task as building wxWidgets on Windows. All you need for it is to have a working compiler, extracted wxWidgets archive, and WXWIN set?
bdad:
Hope I'm not trying your patience too much, I appreciate your help. I think I had internet problems yesterday, Today I had a raft of emails from my bank, going back to 17th Nov, and a registration code for git hub, that expired yesterday.
Anyway, I've reinstalled msys2, (and updated it) and have managed everything up to and including fig 3.1.
I've now confused myself with choices and decisions. The basic requirement is that I want to use codeblocks and a gui design method of generating windows forms, etc., for which I need wxwidgets
I've got to where I've installed the mingw packages, at para 3.3 . Has that built wx widgets, or do I then carry on through to para 3.6.8 and then install codeblocks etc, and do all of section 4, or once wx widgets is built in section 3, I can use that build by just installing code blocks? I need baby steps, but in the right order.
PB:
First, you do not need wxWidgets to create a GUI application for Windows, there are several other choices even for just C++.
Secondly, I hope that by "windows forms" you do not mean Microsoft's Windows Forms, which are available only for .NET.
Thirdly, if you are not sure how to proceed: Why not just follow the guide, including the order in which the individual steps are done? The guide is intended to be followed step by step (with the purpose of each step explained) and if you miss a step, you will not be able to finish it.
Lastly, for building wxWidgets, I would use a parallel build (e.g., with build-library-static-parallel.bat): If you have a computer suited for C++ development, it should speed-up the build considerably. You can tune the number of processors (the number after -j) for your computer, e.g., change the default -j4 to -j2 if your computer has only four cores, so you can still use the computer during the build. But this is also mentioned in the guide...
bdad:
Not microsoft windows forms, but those as mentioned under wxSmith. For me, your guide goes into too much detail, It takes me a while to even understand the terminology, and if I do, then next week it will be forgotten. Not your problem, of course, but I'm more familiar with simpler installation procedures. Anyway, we live and learn.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version