Author Topic: C::B at home not finding wxwidgets from wxDevCPP directory.  (Read 6941 times)

Offline indigo0086

  • Almost regular
  • **
  • Posts: 150
C::B at home not finding wxwidgets from wxDevCPP directory.
« on: January 14, 2008, 02:11:48 pm »
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.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7790
    • My Best Post
Re: C::B at home not finding wxwidgets from wxDevCPP directory.
« Reply #1 on: January 14, 2008, 11:54:19 pm »
Did you compile wxWidgets?

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

Offline eckard_klotz

  • Almost regular
  • **
  • Posts: 201
Re: C::B at home not finding wxwidgets from wxDevCPP directory.
« Reply #2 on: January 15, 2008, 05:55:23 am »
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).
...

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.

Offline indigo0086

  • Almost regular
  • **
  • Posts: 150
Re: C::B at home not finding wxwidgets from wxDevCPP directory.
« Reply #3 on: January 15, 2008, 03:59:05 pm »
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.

Offline byo

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 836
Re: C::B at home not finding wxwidgets from wxDevCPP directory.
« Reply #4 on: January 15, 2008, 09:48:14 pm »
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

Offline indigo0086

  • Almost regular
  • **
  • Posts: 150
Re: C::B at home not finding wxwidgets from wxDevCPP directory.
« Reply #5 on: January 16, 2008, 02:50:14 pm »
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++

Offline Biplab

  • Developer
  • Lives here!
  • *****
  • Posts: 1874
    • Biplab's Blog
Re: C::B at home not finding wxwidgets from wxDevCPP directory.
« Reply #6 on: January 16, 2008, 02:57:46 pm »
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.
« Last Edit: January 16, 2008, 03:03:27 pm by Biplab »
Be a part of the solution, not a part of the problem.