News:

When registered with our forums, feel free to send a "here I am" post here to differ human beings from SPAM bots.

Main Menu

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

Started by indigo0086, January 14, 2008, 02:11:48 PM

Previous topic - Next topic

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

C Programmer working to learn more about C++.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. [url="http://wiki.codeblocks.org"]http://wiki.codeblocks.org[/url]

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:

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

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

indigo0086

It works one one computer with the same setup but not the one ata home.  Can I change the way that CB looks for the wxwidgets directory manually, rather than mess with wxDev-C++

Biplab

A *.devpak file is basically a *.tar.bz2 file. So first rename the devpak file to tar.bz2 file and then extract it to a folder, say foo. Then copy all the header files to foo\include\wx dir and all libraries to foo\lib\<compiler_name>_<lib/dll> dir. That should be enough for C::B to detect and use it.

Please note that the foo\lib\<compiler_name>_<lib/dll> dir also contains some other header files in deep folders and they are necessary to get your app compiled. :)

Edit 1:
The devpak you're using has been compiled under MSYS. Thus the library naming scheme is different. At the moment wxWidgets wizard does not support this naming style. The only way is for you, atm, is to set up the project manually.
Be a part of the solution, not a part of the problem.