User forums > Help
Setting up code blocks so that I can compile wxwidgets programs.
thomas:
It looks like there was a misunderstanding, as you said you intended to set up Code::Blocks to compile with wxWidgets, not compile Code::Blocks itself. But you may nevertheless want to use the nightly build, even more so as you have already downloaded it.
Webwraith is right, you should not install a nightly build over RC2. Make sure you have the 7z files for both the nightly build and required libraries.
You can not copy the ones from RC2, as the libraries in the nightly builds are built in a different, incompatible way.
Unpack everything to the same (empty) directory and you're done.
EDIT:
If you want to use the MinGW compiler (most people do, but you can use a different compiler as well), here is a list of everything you need to download:
http://wiki.codeblocks.org/index.php?title=MinGW_installation#gcc_3.4.4_manual_install
It looks more intimidating than it really is. Just download everything you want and unzip inside an arbitrary location (just make sure you use the same location for everything).
djsbriscoe:
Hi,
I do not want to build code blocks itself just example wxwidgets programs.
This is what I've done so far.
1/ Uninstalled code blocks RC2.
2/ Downloaded the latest build (10-4-06) CB_20060410_rev2334_win32.7z
3/ Downloded wxmsw26u_gcc_cb.7z
Do I just unzip these into a directory called c:\codeblocks?
Is that all I need? How do I configure GCC?
Sorry for all the questions it just seems a bit confusing at the moment.
Thanks,
David.
Michael:
--- Quote from: djsbriscoe on April 11, 2006, 01:27:56 pm ---Hi,
I do not want to build code blocks itself just example wxwidgets programs.
This is what I've done so far.
1/ Uninstalled code blocks RC2.
2/ Downloaded the latest build (10-4-06) CB_20060410_rev2334_win32.7z
3/ Downloded wxmsw26u_gcc_cb.7z
Do I just unzip these into a directory called c:\codeblocks?
Is that all I need? How do I configure GCC?
Sorry for all the questions it just seems a bit confusing at the moment.
--- End quote ---
You can unzip C::B where do you want (just not on an existing RC2 installation :)).
By configuring GCC, once you have started C::B, go in Settings-->Compiler and debugger, select GNU GCC Compiler and check that the pathes are set correctly.
Best wishes,
Michael
thomas:
--- Quote ---2/ Downloaded the latest build (10-4-06) CB_20060410_rev2334_win32.7z
3/ Downloded wxmsw26u_gcc_cb.7z
Do I just unzip these into a directory called c:\codeblocks?
Is that all I need? How do I configure GCC?
--- End quote ---
Yes, except for one more thing. You also need the mingwm10.7z archive (http://prdownload.berlios.de/codeblocks/mingwm10.7z).
Put everything into C:\codeblocks (or any other location) and do a "extract here" on all of them.
To install MinGW, get all the files you need (see above, most people need just the base C/C++ and the debugger packages, but I don't know about you of course, you might want Ada or Java too), and do the same thing (put all into one directory and "unpack here").
If you choose a "typical" location like C:\mingw, then chances are good that Code::Blocks will auto-detect everything without you having to do anything at all.
thomas:
Oh, wait a moment... we never adressed the original question :oops:
After you have done the above, you need to get a working installation of wxWidgets from somewhere.
1. There is a DevPak, but I don't know anything about this (I never use DevPaks). It will probably just do fine, though.
2. The "pristine" way of getting wxWidgets is to download the source and compile it.
One way of doing this is by following the instructions on the page that you have already seen. Although that page actually deals with compiling Code::Blocks, the section "Building wxWidgets" does deliver a fully functional monolithic shared build, which is just fine. You can simply copy the commandline and paste it to a DOS window, hit enter, and go away for 15 minutes :)
You have about 200 options during the wxWidgets build process, but only three are really important:
* SHARED=0 or SHARED=1 -- do you want a DLL (shared) or just static libs?
* MONOLITHIC=0 or MONOLITHIC=1 -- do you one huge thing or several smaller ones?
* UNICODE=0 or UNICODE=1 -- do you want Unicode or not?
The templates coming with Code::Blocks assume a monolithic shared build. That does not mean you cannot do otherwise, but SHARED=1 MONOLITHIC=1 involves the least amount of trouble for starters :)
Unicode or not is a personal choice, I recommend enabling it because it is not terribly expensive and you don't have to think about the problem at a later time when maybe someone complains that your applicatons don't work properly in Russian and Chinese...
If you first start in non-Unicode and have to migrate later, I can promise it will be a pain.
The first time you try to compile a wxWidgets project, you will be asked to set the wx global variable. Point that to where you have wxWidgets, this will set all include and library paths correctly (if you ever move your wxWidgets folder to somewhere else, you just change that variable).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version