Have you considered providing...
Bundling everything looks like a good idea at first, but on the long run, it often causes more problems than it is worth. The big advantage of shipping IDE, compiler, and toolkits separately (even if it is more work to set up) is that you can for example upgrade from gcc 3.4.2 to 3.4.5 simply by deleting the whole MinGW folder and unpacking everything from the MinGW website. You don't touch the IDE, and everything works as before. The same is true for wxWidgets.
When Code::Blocks started out, 2.4.2 was the most recent version. At some point in the middle, we had to develop for 2.4.2 and 2.6.1(2.6.1patch, 2.6.2) in parallel.
Now, how do you develop with two different versions of wx? This is a major pain if everything is bundled and all your includes are in
C:\codeblocks\include. It will never work. On the other hand, if you install them separately to separate locations, then you just change one project variable...
-- So what are you to do now? --
You have wxWidgets on your PC, so far so good. However, the compiler and the linker need to know where you keep your stuff.
Our templates use a
global user variable for that purpose. The advantage is that you only need to set it correctly exactly once.
The first thing you need to know is: Where are your headers and libraries?
If wxdevcpp comes with wx bundled and you have that on your PC, most likely the headers will be in
C:\wxdevcpp\include\wx and the libs will be in
C:\wxdevcpp\lib or a similar place. Don't worry about that
"wx" subfolder (all sources use
#include <wx/somewxheader.h>, so that is OK -- what matters is only where that folder is found).
If you set the wx global user variable to
C:\wxdevcpp, it should work (if the folder layout looks like that).
However, it can happen that your wxdevcpp installation has a different layout (for example, it could put the wx includes into a folder like
C:\wxdevcpp\contrib\wx26 or anything. I don't know anything about that, but that will be easy enough for you to find out
In any case, usually there is a folder
include and a folder
lib somewhere, and they are usually together in the same parent directory. Even if they are in different locations, it does not matter, because you can define
wx.include and
wx.lib separately if needed (see documentation).