User forums > Using Code::Blocks
wxWidgets don't work
DrOli:
Many thanks for the very considerable effort you have provided, and thank you for the extra code. We report on our findings, but really, it looks to us that the MSys2 approach is too heroic at this time, as discussed below.
We've performed various tests with the provided code. Though we are not sure we actually understand the manner in which the provide code is to be used:
1) Attempting to create a new project: we cannot get past the line 363, 1022 etc errors listed previously.
2) Copy the provided files to Templates, no apparent difference.
3) Copy the provided files to one of the "failed" earlier attempts to create a new wx project. This actually launches a project, but then on attempting to compile there are all the same errors we spoke of in our previous experiments with MSys2, most notably, CB's expectation of Dir locations vs. what is actually on the machine, and detailed again in the P.S. below. In addition, there were other "weirdness" as well, but leave those for another time.
We wonder if the "MSys2 experiment" is the best way forward, c.f. perhaps the traditional "CB specific" install approach might be more achievable.
Please keep in mind that all we really need at this point is a CB installation that can make use of standard wx for standard wx projects, such being able to do the "hello world" example here (http://wiki.codeblocks.org/index.php/WxSmith_tutorial:_Hello_world), which relies on a wx installation following the "CB Instructions" (and NOT MSys2), such as those here (http://wiki.codeblocks.org/index.php/Compiling_wxWidgets_3.0.0_to_develop_Code::Blocks_%28MSW%29).
As previously, we were able to follow the "CB instructions" and completed the "make". We have that entire "CB specific make" on the machine, and entirely independent of any MSys or MSys2 installation. It has the monolithic dll, but we can't get CB to see the bits, perhaps due to the "CB make instructions" creating a dir structure that may not be suitable, or we have gone wrong somewhere without knowing it.
We don't understand why "CB instructions" then does not allow us to immediately perform the "tutorial", as should be possible according to CB web page.
Would it make more sense, and be less expensive and achievable, to get the "CB instructions" to work, rather than fork off on a completely different approach (e.g. MSys2)? We don't even know enough to answer that question, so we are relying on CB's expertise.
Please advise on the least expensive direct route to have a sufficient CB/wx installation to perform, say, the CB wx hello world tutorial.
PS
Also, purely as a FYI, the MSys2 bit you had kindly produced, continues to look for wx.h in a dir called \include\wx. Neither MSys2, nor a traditional build from scratch in classical MSys/MingW creates such a Dir. Instead, those installs have a dir \include\wx-3.0\wx. Thus, any and all of the CB/squirl etc bits that have lines like #include "include/wx" will fail, and/or require global replace of some sort. There are other such examples, too, to be left for another day.
Also, Neither MSys2, nor a traditional build from scratch in classical MSys/MingW creates monolithic. Which may explain the script/squirl errors, such as at line 1022, when testing the MSys."X" installs.
stahta01:
I give up because I am failing to communicate with you. I have no idea what I am doing wrong.
But, you give no info that help me help you.
Edit: IMHO, till you know how to create a CB Project that does what you want; you do NOT know enough to edit the CB Wizard to create the CB Project you want.
Edit2: How to use the project I attached as a zip file.
1. You unzip it.
1B. You edit the CB GCC Compiler so it has the correct compiler custom variable COMPILER_PREFIX
2. You open the project using Code::Blocks
3. You try to build the project.
4. You post the full re-build log to figure out what went wrong.
Edit3: Likely things to go wrong.
User failed to add "Additional path" needed to find the correct sh.exe
User failed to add the sed package to MSys2
Edit4: My own thread on CB wxWidgets Wizard http://forums.codeblocks.org/index.php/topic,21094.0.html
Tim S.
DrOli:
I feel your frustration, but in all fairness, we have provided (MANY) detailed reports of exactly what went wrong and why, in which line, etc etc, and what effects various edits had.
... we have now 6-man-days into to this matter, and quite frankly that is a substantial investment considering that an alternative approach might get us to a working solution for much less expense.
... THAT IS why, we are thinking of "dumping the MSys2 approach", and asking about getting the "traditional CB specific wx" install (as per that CB official pages) working, but we don't know why that wont accept the dll's, as reported with some frequency in the previous submissions.
Having said so, and just to demonstrate again exactly what we had reported on multiple occasions, when we follow your (MSys2) instructions, as we had in the past, and showed screen prints (see previous submissions), and detailed reports etc, we repeated the entire process again.
1) Make sure all settings are as per your (MSys2) instructions (see previous screen prints)
2) Create brand new dir/unzip your files.
3) open project, make sure project specific settings are as per your instructions (see previous screen prints)
4) try to build:
... crashes on #include <wx/app.h> in wx30Msys2App.h (see attached log 1)
keeping in mind that the MSys2 (or any MingW) install has
D:\Apps\msys64\mingw32\include\wx-3.0\wx
,, NOT
D:\Apps\msys64\mingw32\include\wx
... so comment out orig line and make change as:
//DrO, #include <wx/app.h>
#include <wx-3.0/wx/app.h>
... no try build again,
... now it crashes in app.h, (see attached log 2, 3)
#include "wx/event.h" // for the base class in App.h
... so try same trick above, comment out orig, and replace with adjusted
//DrO, #include "wx/event.h" // for the base class
#include "wx-3.0/wx/event.h" // for the base class
... now it crashes in event.h (see attached log 4, 5)
... so do same edit as before
//DrO, #include "wx/defs.h"
#include "wx-3.0/wx/defs.h"
... try build again,
... this goes on and on, exactly as it did in all the previous experiments, which we provided in detail in the previous submissions.
... DECIDED to set extra search path in Project compiler and linker settings: D:\Apps\msys64\mingw32\include\wx-3.0
... and also "undid" all of the custom edits above
... closed CB, and restarted CB
... tried to open project, this time, big surprise, get three dialogue boxes to the effect:
"cc1plus.exe - Unable to locate component"
"This application has failed to start because libgmp-10.dll was not found....."
All of this sort of behaviour had been reported repeatedly with repeated experiments in the past. If you still think MSys2 is the way to go, OK, but we really need something that works soon ... remember, at this point we are just trying to see if we can get the CB Hello World Tutorial working.
... AND, please explain why we should not get the "traditional CB Specific" approach to work, instead of spending all this time/money on the MSys2 approach.
... in particular, if do this (http://wiki.codeblocks.org/index.php/Compiling_wxWidgets_3.0.0_to_develop_Code::Blocks_%28MSW%29), then how come we can't this (http://wiki.codeblocks.org/index.php/WxSmith_tutorial:_Hello_world), particularly given the many results/tests etc we have submitted on that approach.
PS. as per usual the blog limits two achievements per post, so will need to add some posts for the entire collection of jpgs cited above.
DrOli:
attachments 3, 4
DrOli:
The blog is preventing the attachments/jpgs for some odd reason ... I'll try posting the jpgs later
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version