- MinGW is one of the 15 C::B supported compilersIt is true, but there are 2 version of wxwidgets for Windows one with mingw and one without it, just include a precompiled wx only in the mingw release :)
I think it is too specificYou're right about that, maybe i can compile it in those options:
Compiling wxWidgets is not so complicated...It's easy when... you know (as I do). For a newbie, it's difficult. Think about beginners !
Yes, when I first compiled wx, I succeeded in 5th or 7th time and it definately didn't seem to be easy.QuoteCompiling wxWidgets is not so complicated...It's easy when... you know (as I do). For a newbie, it's difficult. Think about beginners !
Think about beginners !So nice ! Just avoid people thinking ! Solve problems for them, that way they will progress and learn !
Just imagine: you're a beginner and you install a full-bundled Code::Blocks. Then you create a project with the wizard, you compile/link, and your exe starts ! Everything would be so easy and straightforward !
Just look at the number of people in this forum that try to compile wxWidgets, or install C::B and don't know how to link their exe based on wx. Some of them are discouraged and don't go farther.
QuoteYes, when I first compiled wx, I succeeded in 5th or 7th time and it definately didn't seem to be easy.QuoteCompiling wxWidgets is not so complicated...It's easy when... you know (as I do). For a newbie, it's difficult. Think about beginners !
I think that in the most cases it does not work because the user thinks he can do it without reading the doc's.My hero :D
And it's almost always good to know what you do before you start.
People have to learn that reading documentation is one of the most important things if you want to work efficiently with any SDK.
Or you get frustrated because nothing works as expected and you spend much time in trying out things, that work in a much easier way if you know how.
When I first compiled wxWidgets I used this entry of the nightly cookbook (http://wiki.codeblocks.org/index.php?title=Nightly_Cookbook#wxWidgets),Amen.
and it succeeded the first time.
Amen too :DWhen I first compiled wxWidgets I used this entry of the nightly cookbook (http://wiki.codeblocks.org/index.php?title=Nightly_Cookbook#wxWidgets),Amen.
and it succeeded the first time.
My opinion:
We won't do anyones homework here. If you ever want to develop with wxWidgets (this includes development for C::B) you *really* should be able to at least compile wxWidgets. Literally millions of people (it's a wide spreaded toolkit) did it and succeeded with the so-much-important lessons learned. There is tons of help around but of course one needs to 1.) read, 2.) think and finally 3.) understand. It's so easy!
This of course includes me. I did it the first time as Jens said and succeeded, too.
And by the way, building wxWidgets is not so complicatedAnd no so easy either...
Soon I'll post the new version of wx precompiled, with the above 4 configurations. Once it has been posted, do what you want with it: add to the next C::B release, post a link in the wiki, or just do nothing
Well, guys, it's not a technical issue, it's a "marketing" issue.
I'm afraid there is here the infamous Linux syndrom [which I thought was declining] : Read the f***g manual (even for matters not easy for newbies).
But as you don't care of this stuff, I give up.
I'm afraid there is here the infamous Linux syndrom [which I thought was declining] : Read the f***g manual (even for matters not easy for newbies).You forgot Read the f***g wiki and Search the f***g forums
But as you don't care of this stuff, I give up.
If we provide pre-built wx libs then why shouldn't we provide qt libs too? And boost? And whatever else?Because C::B is based upon wx and because C::B embeds wxSmith (a RAD tool for wx)...
Finally, did it ever occur to you that the wx team itself does NOT provide windows binaries of their own product?Dit it ever occur to you that wxDevCpp is an integrated tool providing wx Windows binaries ?
You have to understand that this is out of this project's scope. We provide the tool (C::B) and as much documentation as is possible for us to write/maintain (considering this is an open-source project and people do work on it on their free time). We also provide support for the project through these very forums. Support that is relevant to our toolWell, this a reason I admit much better than: "User has to cope him/herself with wx compilation and it's very nice for him/her since it's an excellent way to learn wx". You want to focus on core activity (developping C::B) and not get involved into something peripheral. It's true time is limited...
If inventore123 (or anyone else) is willing to pre-copile and provide wx libs (or any other lib) for others to use, they 're of course free to do so and can also "advertise" it in these forums so others become aware.OK. I'm happy :D! And I think it deserves a link from wiki and main site, too.
Ok, here are the precompiled versions:Good job !
But I would also have done the following :I would like peace in the world.
I really can't believe you say so...Well, I dont't know who Alexis is, but to me it does not seem to be a noob that wants other to do his homework. It seems another one, like me, that was surprised in finding that the release of C::B included wxSmith, but not wxWidgets, and thinks that a 'plug and play' release will attract more users to this good IDE.
wx/msw/wx.rc: No such file or directory
can't open icon file `wx/msw/std.ico': Invalid argument
preprocessing failed.
=== Build finished: 3 errors, 0 warnings ===
Compiling: resource.rc
C:\DOCUME~1\fede\MYDOCU~1\CODEBL~1\dll_test\resource.rc:3:24: wx/msw/wx.rc: No such file or directory
gcc: Files\CodeBlocks\wxWidgets-2.8.8\include: No such file or directory
gcc: Files\CodeBlocks\wxWidgets-2.8.8\lib\gcc_dll\mswu: No such file or directory
windres.exe: can't open icon file `wx/msw/std.ico': Invalid argument
windres.exe: preprocessing failed.
Process terminated with status 1 (0 minutes, 0 seconds)
3 errors, 0 warnings
I would like peace in the world.Peace with you, MortenMacFly.
I really can't believe you say so... why don't you do what you want yourself ? You make me feel like a slave. Anything else you want us to do...?!I'm afraid you don't get the point. I've been knowing how to setup my wx/CB environment on WinXP and Linux for a while.
Well, I dont't know who Alexis is, but to me it does not seem to be a noob that wants other to do his homework. It seems another one, like me, that was surprised in finding that the release of C::B included wxSmith, but not wxWidgets, and thinks that a 'plug and play' release will attract more users to this good IDE.EXACTLY ! This is exactly my situation.
Anyway, can someone explain me why, if I move the wx folder in "C:\Program files\Codeblocks" (a path with one space), I can't compile anything? Here are the errors:inventore123, what is your toolchain, and where is it installed ?
windres --version
GNU windres (GNU binutils) 2.18.50.20080109
Copyright 2007 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) any later version.
This program has absolutely no warranty.
-------------- Build: Debug in dll_test ---------------
mingw32-g++.exe -pipe -mthreads -D__GNUWIN32__ -D__WXMSW__ -DWXUSINGDLL -DwxUSE_UNICODE -Wall -g -D__WXDEBUG__ -I"C:\Program Files\CodeBlocks\wxWidgets-2.8.8\include" -I"C:\Program Files\CodeBlocks\wxWidgets-2.8.8\contrib\include" -I"C:\Program Files\CodeBlocks\wxWidgets-2.8.8\lib\gcc_dll\mswud" -c "C:\Documents and Settings\fede\My Documents\codeblocks\dll_test\dll_testMain.cpp" -o obj\Debug\dll_testMain.o
windres.exe -i C:\DOCUME~1\fede\MYDOCU~1\CODEBL~1\dll_test\resource.rc -J rc -o obj\Debug\resource.res -O coff -I"C:\Program Files\CodeBlocks\wxWidgets-2.8.8\include" -I"C:\Program Files\CodeBlocks\wxWidgets-2.8.8\lib\gcc_dll\mswud"
C:\DOCUME~1\fede\MYDOCU~1\CODEBL~1\dll_test\resource.rc:3:24: wx/msw/wx.rc: No such file or directory
gcc: Files\CodeBlocks\wxWidgets-2.8.8\include: No such file or directory
gcc: Files\CodeBlocks\wxWidgets-2.8.8\lib\gcc_dll\mswud: No such file or directory
windres.exe: preprocessing failed.
Process terminated with status 1 (0 minutes, 1 seconds)
2 errors, 0 warnings
The problem of spaces in wx path seems NOT a bug of C::B, but a bug of windres.exe, because C::B correctly surround the path with "".That is true. You now have 2 options:
Last thing, can you confirm me that the path for #wx global variable MUST be an absolute pathThat's true. Hence for the "childs" (like include etc...) you can use relative path's again - just like a recursion. This way you need to change only one path if you are on another platform.