Code::Blocks Forums

User forums => Help => Topic started by: carnykur on October 17, 2006, 09:14:01 am

Title: wxwidgets - can't setup project
Post by: carnykur on October 17, 2006, 09:14:01 am

i'm trying to setup wxWidgets project. i'm on win xp. i downloaded wxwidgets and mingw. installed and compiled. i noticed, that mingw32-make did not produced any dll but also did not report errors (i did not find any). it only generated lots of object files and lib files. in c::b wxwidgets wizard i enter wx instalation dir and at first it takes it, but finally it says that wx is not properly configured and project would not build.

i've got two questions:
1.)is wxwidgets prepared to be used in c::b project or what should i do? i did all that was adviced in wx instal text file (mingw32-make ....).
2.)what directory should i enter to wxwidgtets wizard?

Title: Re: wxwidgets - can't setup project
Post by: stahta01 on October 17, 2006, 10:59:49 am

did you follow these directions for wxWidgets? http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows

If you used the above directions you used you should find an dll in the folder lib\gcc_dll wxmsw26u_gcc_custom.dll (This assumes Unicode NON-debug Build)

2. The #wx directory should have folders called include, build, lib and the others that go with them right under it.

If you are getting an error creating the DLL, I used directions from this URL to get around it for me.
http://www.mameworld.net/mrdo/compile.html

Here's the part from the link that matters.

You should now have a folder with the nine subfolders as shown on the right. Now, extract the dx80_mgw.zip to your C:\MinGW folder. Make sure you have the option Extract Relative Paths or similar checked in your unzip utility. This is because each file is archived using the same folder structure, and you want the right files to be in the right folders. If you are asked to overwrite files at anytime, do so.

dx80_mgw.zip is at this URL http://alleg.sourceforge.net/files/dx80_mgw.zip

I tend to get the error doing NON DLL or Debug builds, but I did get it once on the regular DLL build.
Since, I build Mame alot it could be I always used a patch minGW before that one failure.

Tim S