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).