User forums > Help
How to build wxwidgets-2.6.3 to work with code::blocks
ALLs:
--- Quote from: Lukas on June 15, 2006, 08:39:36 am ---The u of -lwxmsw26u means it's trying to link the unicode version. Check if you have a libwxmsw26 and if so link to that instead.
i.e replace wxmsw26u with wxmsw26 in the build options/linker
--- End quote ---
yes, i now deselect enable unicode in wizard and it working :shock:
thx on help...
Michael:
--- Quote from: Didier69 on June 15, 2006, 08:24:28 am ---Hi,
First I installed mingw last version with the candidate option, then I used this wiki page and it worked for me ;).
--- End quote ---
Hello,
Or here :):
http://forums.codeblocks.org/index.php?topic=1701.0
Best wishes,
Michael
wittend:
I really like what I see in the Code::Blocks IDE. I particularly want to use it with WxWidgets. The combination seems to be just what I need for two high priority projects, and probably for the next generation of some others.
Unfortunately, of the many programming environments that I use, I have never encountered anything like the difficulty I have had attempting to get this combination configured to correctly compile trivial programs. There is a large amount of well meaning help available, including the documents on this forum, the Wiki, and the files included with the software. Unfortunately, they are frequently contradictory, out of date, or simply at odds with the results that I obtain.
I prefer to use up to date, stable software, and I ordinarily avoid the latest beta's. But both Code::Blocks and its most obvious alternative, Dev-C++ seem to be on a Moebius-strip glidepath to version 1.0. I'm sure that some of my problems derive from the way wxWidgets is packaged and documented for distribution, as well. At this point, the only way that I seem to be able to get useful compiles of MinGW/wxWidgets apps is to do manual command line builds in MSYS using the Makefiles built by configure as examples.
I don't believe that my current expectations are exotic. I just want to be able to design and build straightforward wxWidgets 2.63 apps for (at present) the Win32 environment. I don't have any reason to want to build Code::Blocks from source, so I have used the installer version. Once installed, I want to build unicode apps, staticly linked, at least, but DLL-based would be a nice option, and debug versions of both static & DLL based apps would be icing on the cake.
I am currently using:
CodeBlocks that identifies itself on the startup page as: Version 1.0 revision 2061 (gcc 3.4.4 Windows/unicode, build: Feb 22 2006 16:56:26)
mingw32-make -v returns 3.80
The wxWidgets version that I am compiling indicates that it is 2.63_1
I am not interested in ANSI builds.
I am using an AMD64 based PC running Windows 2003 with 2G ram and ~ 500G of disk, mostly free.
I have installed all the components that are claimed to be required. I have done this repeatedly after exorcising every trace of previous attempts. I have done the whole process on two different machines (gotta get a new laptop - 2hrs to build each wxWidgets library set is too long to bear).
The farthest that I have been able to get working with the IDE is to the point where I can create a default wxWidgets app using the template, add nothing to it - just build it, and I get a horror story of linkage errors. These *appear* to my unaided eye to be due to a fundamental problem with calling convention or some such. For ex:
mingw32-g++.exe -LD:\bin\CodeBlocks\wx\wxWidgets-2.6.3\lib\gcc_dll -LD:\bin\CodeBlocks\wx\wxWidgets-2.6.3\lib -LD:\bin\CodeBlocks\lib -LD:\bin\CodeBlocks\wx\wxWidgets-2.6.3\lib -o wxwidgets_static.exe .objs\main.o -lwinspool -lwinmm -lshell32 -lcomctl32 -lctl3d32 -lodbc32 -ladvapi32 -lwsock32 -lopengl32 -lglu32 -lole32 -loleaut32 -luuid D:\bin\wxWidgets-2.6.3\lib\libwx_mswu-2.6.dll.a D:\bin\wxWidgets-2.6.3\lib\libwxzlib-2.6.a D:\bin\wxWidgets-2.6.3\lib\libwx_mswu-2.6.dll.a D:\bin\wxWidgets-2.6.3\lib\libwxexpat-2.6.a D:\bin\wxWidgets-2.6.3\lib\libwxjpeg-2.6.a D:\bin\wxWidgets-2.6.3\lib\libwxpng-2.6.a D:\bin\wxWidgets-2.6.3\lib\libwxregexu-2.6.a D:\bin\wxWidgets-2.6.3\lib\libwxtiff-2.6.a -mwindows
Info: resolving wxStringBase::npos by linking to __imp___ZN12wxStringBase4nposE (auto-import)
Info: resolving wxAppConsole::ms_appInstance by linking to __imp___ZN12wxAppConsole14ms_appInstanceE (auto-import)
Info: resolving wxFrame::sm_eventTable by linking to __imp___ZN7wxFrame13sm_eventTableE (auto-import)
Info: resolving _wxFrameNameStr by linking to __imp__wxFrameNameStr (auto-import)
...
then:
Checking for existence: D:\Work\Commercial\test\wxwidgets_static.exe
Executing: "D:\Work\Commercial\test\wxwidgets_static.exe" (in D:\Work\Commercial\test\.)
Process terminated with status 128 (0 minutes, 14 seconds)
which dies horribly with the message:
"The application failed to initialize properly (0xc0000005). Click OK to terminate the application."
This is a seems like a very promising platform, but looking back it seems the I have been pissing away time on this for at *least* 6 mo, usually for 2-3 days/mo until I get so frustrated that I have to go on to other things. I am either too dense to float or some real attention needs to be given to default setups, binary distributions and other issues that keep this from being a more popular solution.
Please understand, I do realize and appreciate the amount of effort that goes into a project like this. Most of it is *so* good, that It is maddening when I cannot use it.
Dave Witten
Michael:
Hello,
If I were you, I would:
1) Update and re-build wxWidgets with Patch 2 if you are still using a version with Patch 1.
2) Update C::B to the latest revision (nightly build or build by yourself).
3) Instead of using a template, try to generate a new project and set coorectly the include and lib directory (also set correctly the type of application you are developing, e.g., dll).
Best wishes,
Michael
PS.: Search also in the forum. I am quite sure that you will find some useful info.
wittend:
--- Quote from: Michael on July 05, 2006, 07:34:20 pm ---Hello,
If I were you, I would:
1) Update and re-build wxWidgets with Patch 2 if you are still using a version with Patch 1.
2) Update C::B to the latest revision (nightly build or build by yourself).
3) Instead of using a template, try to generate a new project and set coorectly the include and lib directory (also set correctly the type of application you are developing, e.g., dll).
Best wishes,
Michael
PS.: Search also in the forum. I am quite sure that you will find some useful info.
--- End quote ---
Will do... I see that the version on my main system is older that the one I worked with on another machine yesterday. Aside from my venting, though, there seems to be more than the usual margin for error. When you set out to set this up for the first time, A person who simply needs to get some work done has difficulty identifying the correct path to follow.
-- Dave
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version