User forums > Using Code::Blocks
Compiling a wxWidgets application - wx/setup.h: No such file or directory
stahta01:
--- Quote from: ggpr on March 13, 2008, 04:05:25 pm ---I also think theres a setup0.h hidden in the directorys somewhere that can be placed where it needs to be
--- End quote ---
The problem is normally the user did not use mingw32-make or some other make to compile wxWidgets.
Copying the setup0.h does not fix the problem!!
Tim S
schroeder:
...so.... how does this story end? ;)
[I ask this because I've got stuck exactly in the same problems svaens has encountered... so I'd like very much to know if this story ends well :)]
P.S.:
--- Quote from: Biplab on August 09, 2007, 10:09:25 am ---C::B's wxWidgets wizard does not support MSYS-MinGW compiled wxWidgets lib. On Windows, please compile wxWidgets from command prompt which wizard can detect and configure.
--- End quote ---
I'm sorry but it's not my case. Setup:
* MinGW 3.4.5 installed in a directory with no spaces in the path (this, just to exclude the possibility that the issues amount to "something" - whatever it can be, a compiler, a linker, etc. - unable to find "something else") and, in fact, currently working, for instance, just with CodeBlock in the "console" mode
* wxWidgets 2.8.7 installed and compiled with the utmost care (that is, following exactly the instructions they put on the official README/INSTALL), both in the "pure MinGW" mode (that is, with 'mingw32-make -f makefile.gcc BUILD=debug(release)') and in the "MSYS" mode (=>./configure - make)
Notwithstanding this, in both cases things run as told by svaens. The wizard doesn't recognize the installation completely, and the compile process halts. I've been wondering why for the last two days, without being able to get to any solution ^^
BTW, svaens: the "wx/setup.h: No such file or directory" issue is quickly fixed by simply copying the 'setup.h' file, which by default is laid aside unhelpfully in a subdirectory of the '\build\msw\the-name-you-choose-for-this' dir where you actually built the compiler-specific release, to the '\include' directory, where it's actually needed.
Unfortunately, however, this only makes the compiler stop complaining about not finding the header where it should be: but it doesn't fix the other problems ^__^
stahta01:
--- Quote from: schroeder on March 16, 2008, 07:35:02 pm ---mingw32-make -f makefile.gcc BUILD=debug
--- End quote ---
Please give the exact command used and someone should be able to help you.
The options needed to be picked in the wizard must be the correct ones as determined by the ones used by mingw32-make options.
Tim S
TDragon:
Check out the wxWindowsQuickRef.
schroeder:
--- Quote from: TDragon on March 17, 2008, 05:21:15 am ---Check out the wxWindowsQuickRef.
--- End quote ---
Thank you for the very interesting link, which I had previously missed.
At a first glance, however, it seems that until now I've followed the correct procedure, at least for what concerns the "Build wxWidgets" section.
I have just a curiosity: why do you consider the "MONOLITHIC=1" option to be better?
--- Quote from: stahta01 on March 17, 2008, 01:15:47 am ---
Please give the exact command used and someone should be able to help you.
The options needed to be picked in the wizard must be the correct ones as determined by the ones used by mingw32-make options.
Tim S
--- End quote ---
The exact command was the one I've written above: from inside the '<wxWidgets>\build\msw ' directory (to use the same name convention adopted in the tutorial linked above)
--- Code: ---mingw32-make -f makefile.gcc BUILD=release
--- End code ---
with the 'SHARED=1' and 'UNICODE=1' assigned by modifying the 'config.gcc' file instead of giving it as an option in the command line (which could easily be the reason for all the hassle). And in fact, the compilation process ends well, and the libraries seem to be all there, where they're supposed to be.
Or at least, this is what I think: for I admit I'd actually find very useful to have, in the wxWidgets' README or HOWTO-INSTALL, sort of a recapitulation of how a well-built distribution should look like. I mean, something like the "summary of what you should have inside your release, once you've unzipped it to where you like" recommendation that the developers of MinGW put in their releases...
Anyway, as soon as possible I'm going to make other experiments. I'll post the results here (but only if they'll be positive ;D )
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version