User forums > Using Code::Blocks
wxWidgets don't work
BlueHazzard:
This is all a lot text and just to make sure i understand everything:
1) You are using Windows XP
2) Your "normal" approach to build wxWidgets is to go with msys and the configure script provided by wxWidgets?
3) To clear things up: as far as i understand the "normal" way to build wxWdigets under windows is the way how it is described in our wiki (see in install.txt the point "* Using plain makefiles:"from the wxWidgets documentation. In a "normal" case you won't install all the unix tools in a windwos environment.)
--- Quote ---these instructions do NOT install the resultant dll's etc in the expected location
--- End quote ---
Under windows i wont expect the libraries to be installed in /lib etc... subdirectories. This is a unix approach...
BUT: this is not the point we are talking about, so i won't discuss this future :) .
4) I don't think that codeblocks "needs" a monolithic build. I have used codeblocks also with non monolithic builds. You simply have to remove the tick at the "wxWidgets is build as a monolithic library" at the 8. Wizard page.
Your problem, as far as i can tell, is: You use the "configure" approach to install wxWidgets under windows and codeblocks does not detect it with its default scripts?
So we need a second search script, that can detect the "configure" approach?
DrOli:
No, that seems to miss crucial points. As indicated in the previous messages, we have tried MANY MANY permutations. Roughly speaking they fall into four completely independent efforts. We have tried these efforts under both WinXP64 and Win7/64, but mostly WinXP64.
As indicated repeatedly, one of those key entirely independent efforts was to use what we keep referring to as the "CB instructions", and which we had carefully cited in our original post as coming from here (http://wiki.codeblocks.org/index.php/Compiling_wxWidgets_3.0.0_to_develop_Code::Blocks_%28MSW%29). We understand that to be CB special required install process.
Our previous submissions include some adjustments required to the make the CB instructions work with 3.x (e.g. gnu++11, etc).
The make appeared to work. However, as repeatedly emphasised, it "makes" the files in a highly unusual directory structure. We don't know if that is one of the reasons why we can't get it work in CB.
To be clear, once again, this is completely and entirely independent of any of the other efforts we tried via any flavour of MinGW or "config" etc etc.
Using the "CB instructions", when we try to create a wx project, and after some fiddling for the wizard to even accept the (CB specific) wx.h location etc, the wizard allows us to get past the next couple of dialogues, eventually to arrive at something like:
SquirrelFunction<> call failed
AN ERROR HAS OCCURED [arith op + on between 'null' and 'instance']
CALLSTACK
*FUNCTION [OnLeave_WxConf()] D:\Apps\CodeBlocks\share\codeblocks/templates/wizard/wxwidgets/wizard.script line [363]
LOCALS
[lib_rel_name] INSTANCE
[lib_deb_name] INSTANCE
[lib_name] NULL
[lib] INSTANCE
[lib_suffix] NULL
[lib_unic_suffix] INSTANCE
[lib_wxver] INSTANCE
[lib_prefix] NULL
[fwd] true
[this] TABLE
We have no idea what that means, and cant find any way to make progress along those lines. Though, it would not surprise us to learn that this may mean it can't find the dll's etc, possibly since the "CB Instructions" produce a somewhat unusual dir structure for the "make" results ... and likely we are missing some information.
As for "monolithic", clearly the CB specific instructions from the CB web page cited insist on monolithic.
We were under the impression from previous responses that editing the wizard was the suggested fix. Based on that, which was in connection with a MinGW install (c.f. a "CB make"), We had said that the only way we could actually get CB to get to a "proper" wx project, where CB actually shows the "drawing area", cpp's, etc was by editing the wizard, and using a MingW installation, though that posed new problems, and we did not expect that work for the reasons already stated previously.
To summarise, we have tried many different entirely independent approaches, initially focusing on the "CB instructions", but later also testing MinGW approaches.
We are happy to help/try any approach (be it "CB make", MSys config, whatever), but again we are "math geeks", not "IT geeks", and we need at least some assistance to move forward, and apparently many crucial bits are in CB's internal machinery/files.
stahta01:
I tried to recreate my past steps and failed using MSys2 GCC 5.3; I am wondering what GCC version you are using and I will try using your version on my next attempt.
FYI: I tried using the [code::blocks] default MinGW GCC compiler; instead of using the Cygwin GCC as I normally do.
What CB Compiler are you trying to edit to use the MSys2 GCC compiler?
What Msys2 GCC version are you using?
Edit: Decided my MSys2 installation might be corrupt deleting it and starting over.
Tim S.
stahta01:
I succeeded; I had a cut/paste error that I did NOT notice for about 2 hours.
Link to my draft instructions https://github.com/stahta01/cb_misc/blob/master/Notes/CB%20setup%20for%20MSys2%20wxWidgets.txt
Edit: I used "Compiler Custom Variables" for the two variables that needed to have forward slashes because I had issues when I tried either CB Global vars or Project Custom vars.
Edit2: Build log
--- Code: ----------------- Clean: Debug in wx30Msys2 (compiler: GNU GCC Compiler MSys2 MinGW64)---------------
Cleaned "wx30Msys2 - Debug"
-------------- Build: Debug in wx30Msys2 (compiler: GNU GCC Compiler MSys2 MinGW64)---------------
x86_64-w64-mingw32-g++.exe -Wall -pipe -mthreads -D__GNUWIN32__ -D__WXMSW__ -DWXUSINGDLL -DwxUSE_UNICODE -g -IC:/Apps64/MSys2/mingw64/lib/wx/include/msw-unicode-3.0 -IC:/Apps64/MSys2/mingw64/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXMSW__ -fpermissive -c C:/SourceCode/test/wx30Msys2/wx30Msys2App.cpp -o obj/Debug/wx30Msys2App.o
x86_64-w64-mingw32-g++.exe -Wall -pipe -mthreads -D__GNUWIN32__ -D__WXMSW__ -DWXUSINGDLL -DwxUSE_UNICODE -g -IC:/Apps64/MSys2/mingw64/lib/wx/include/msw-unicode-3.0 -IC:/Apps64/MSys2/mingw64/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXMSW__ -fpermissive -c C:/SourceCode/test/wx30Msys2/wx30Msys2Main.cpp -o obj/Debug/wx30Msys2Main.o
x86_64-w64-mingw32-g++.exe -o bin/Debug/wx30Msys2.exe obj/Debug/wx30Msys2App.o obj/Debug/wx30Msys2Main.o -LC:/Apps64/MSys2/mingw64/lib -pipe -Wl,--subsystem,windows -mwindows -lwx_mswu_xrc-3.0 -lwx_mswu_webview-3.0 -lwx_mswu_html-3.0 -lwx_mswu_qa-3.0 -lwx_mswu_adv-3.0 -lwx_mswu_core-3.0 -lwx_baseu_xml-3.0 -lwx_baseu_net-3.0 -lwx_baseu-3.0 -mthreads
Output file is bin\Debug\wx30Msys2.exe with size 866.95 KB
Process terminated with status 0 (0 minute(s), 8 second(s))
0 error(s), 0 warning(s) (0 minute(s), 8 second(s))
--- End code ---
Tim S.
Deleted attachment because it is a waste of bandwidth to try to help this person we both speak English; but, we do NOT communicate.
DrOli:
Many thanks for that. My dir structure is a little different, so I made the appropriate changes, but still failed.
1) My MSys2 Dir structure is shown in "wx MSys2 Dir struct 1.jpg" attached
2) I set the global vars as shown in "wx MSys2 Glb Var 1.jpg" attached.
3) My toolchain is as per "wx MSys2 Tool Chain 1.jpg" attached
4) I set the custom (toochain) vars as per "wx MSys2 Custom Var 1.jpg", attached.
5) When I try to create a project, it fails on the dialogue "wx MSys2 loc1.jpg", attached.
... so did not get to setting the project specific custom vars
... since I can only add two attachments at a time, I will add to the additional attachment to two Posts immediately following
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version