User forums > Using Code::Blocks

C::B at home not finding wxwidgets from wxDevCPP directory.

(1/2) > >>

indigo0086:
I have my Mingw and wxWidgets install library located in the wxDevC++ directory because there was a conflict with the standard wxwidgets and wxDevC++ install so I had to uninstall the default Mingw.  Now my CB can read mingw and compile from the wxDevC++ but when I go to create a wxWidgets project and try to point it the environment variables to the wxwidgets directory (including the include and lib part) it says it seems like a valid directory but can't find the files.  Now te one I have installed on another computer works fine and reads from the wxWidgets directory, just not the one at home.

stahta01:
Did you compile wxWidgets?

Tim S

eckard_klotz:
Hello Indigo0086.

If you use the tools of wxDevC++ I think you have installed evryting  by using the devpak-tool.

On one Side of "Devpak.org" (http://devpaks.org/details.php?devpak=159) you can find the following tip:


--- Quote ---The DevCpp Packman tool fails to properly unpack the devpak package (see http://andre-simon.de/doku/wxwidgets/devpak_install.html how to unpack it manually).
...
--- End quote ---

I hope it helps you.

Another Question is, do you have to set some global variables and compiler-settings in C::B also? I don't realy know but this may be point of interest for you also.

Regards,
             Eckard Klotz.

indigo0086:
It unpacks properly because I can compile a wxwidgets program with wx-devcpp after usign the devpak, but when I try to point Code::Blocks to the directories it says it can't.

byo:
That's probably because devpacks use different directory structure for wxWidgets than when you compile wx from source using MinGW. C::B preffers the MinGW solution when you create project so you'll have to manually adjust directories in this case.

Regards
   BYO

Navigation

[0] Message Index

[#] Next page