Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
[Windows] precompiled wxWidgets in next release
inventore123:
I'm using C::B 8.02 (Official release that includes MinGW)
The IDE is installed in "C:\Program files\CodeBlocks"
MinGW is installed in "C:\Program files\CodeBlocks\MinGW"
now, if i put wxWidgets directory in "C:\wxWidgets-2.8.8" everything works fine (And this is what I wrote in Readme.txt)
BUT if I move the wx directory in "C:\Program files\CodeBlocks\wxWidgets-2.8.8" I cannot compile anything from C::B (but if I try to compile a project from the command line, with a Makefile, it works. So it seems a C::B bug)
Moving the wx directory inside C::B's directory will make the installation cleaner, centralizing all data in one folder, and I think is necessary before wrapping everything in a setup.exe
Alexis, where have you installed wx?
Any help is appreciated :)
stahta01:
What version of MinGW windres?
It may have problems with spaces or C::B might not be passing the command to it right.
windres --version
I suggest turning on full compiler logging and looking at the command.
Tim S
inventore123:
--- Code: ---windres --version
GNU windres (GNU binutils) 2.18.50.20080109
Copyright 2007 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) any later version.
This program has absolutely no warranty.
--- End code ---
I'll try to enable full logging to see if it is a bug of C::B or MinGW.
Anyway, I've spotted another bug: I can't specify a relative path for the #wx global variable :(
It would be very esasy to put the wxWidgets' folder inside CodeBlocks folder and just use "./wxWidgets-2.8.8" as path. But if I do it C::B outputs *many* error lines about not finding wx's .h files :(
inventore123:
Here is the full log:
--- Code: ----------------- Build: Debug in dll_test ---------------
mingw32-g++.exe -pipe -mthreads -D__GNUWIN32__ -D__WXMSW__ -DWXUSINGDLL -DwxUSE_UNICODE -Wall -g -D__WXDEBUG__ -I"C:\Program Files\CodeBlocks\wxWidgets-2.8.8\include" -I"C:\Program Files\CodeBlocks\wxWidgets-2.8.8\contrib\include" -I"C:\Program Files\CodeBlocks\wxWidgets-2.8.8\lib\gcc_dll\mswud" -c "C:\Documents and Settings\fede\My Documents\codeblocks\dll_test\dll_testMain.cpp" -o obj\Debug\dll_testMain.o
windres.exe -i C:\DOCUME~1\fede\MYDOCU~1\CODEBL~1\dll_test\resource.rc -J rc -o obj\Debug\resource.res -O coff -I"C:\Program Files\CodeBlocks\wxWidgets-2.8.8\include" -I"C:\Program Files\CodeBlocks\wxWidgets-2.8.8\lib\gcc_dll\mswud"
C:\DOCUME~1\fede\MYDOCU~1\CODEBL~1\dll_test\resource.rc:3:24: wx/msw/wx.rc: No such file or directory
gcc: Files\CodeBlocks\wxWidgets-2.8.8\include: No such file or directory
gcc: Files\CodeBlocks\wxWidgets-2.8.8\lib\gcc_dll\mswud: No such file or directory
windres.exe: preprocessing failed.
Process terminated with status 1 (0 minutes, 1 seconds)
2 errors, 0 warnings
--- End code ---
The problem of spaces in wx path seems NOT a bug of C::B, but a bug of windres.exe, because C::B correctly surround the path with "".
Ok, now that we know where the bug is, any suggestion about what to do?
also any suggestion about why relative path don't work?
MortenMacFly:
--- Quote from: inventore123 on July 11, 2008, 03:35:22 pm ---The problem of spaces in wx path seems NOT a bug of C::B, but a bug of windres.exe, because C::B correctly surround the path with "".
--- End quote ---
That is true. You now have 2 options:
1.) Use a later version of windres (binutils) but then other things might get broken.
2.) Define the path to wx as 8.3 type (short path name). You can seti up accordingly in your project options or (if it is coming from a global variable) within this setup.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version