User forums > Help
wxWidgets 2.6 (MSW, GCC) installation instructions
wittend:
Evidently I was not alone in my concerns - the 'nightly' build from last night has many of these issues resolved or at least much improved. Things are *much* more clearly labled at some of the critical points that were deviling me. There are also improved instructions on how to proceed through the process.
I haven't got wxWidgets installed sanely yet, and I still have not successfully compiled anything, but at least I can see some shapes in the darkness.
Thanks,
--dave
wittend:
Ok, there is still something that is I'm not comprehending. I have nuked my CodeBlocks & wxWidgets & MinGW installs and reinstalled everything as recommended by the good advisors on this forum. This time I used the MinGW 5.0.2 installer, which has backed me off to gcc v 3.4.2 (from 3.4.4) and installed wxWidgets 2.6.2 instead of 2.6.3-rc1.
Following the directions on the page "Compiling wxWidgets 2.6.1 to develop Code::Blocks (MSW)" as instructed, I encounter a problem I grappled with when I built wxWidgets the last time. Either command (at a cmd.exe prompt):
D:\bin\CodeBlocks\wx\build\msw>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean
- or -
D:\bin\CodeBlocks\wx\build\msw>make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0
is greeted with derision by the makefiles, beginning in the general form of:
if not exist gcc_mswdll mkdir gcc_mswdll
C:\DOCUME~1\ADMINI~1.OUT\LOCALS~1\Temp\make13042.sh: command not found: not [1]
if not exist ..\..\lib\gcc_dll mkdir ..\..\lib\gcc_dll
C:\DOCUME~1\ADMINI~1.OUT\LOCALS~1\Temp\make13043.sh: command not found: not [1]
if not exist ..\..\lib\gcc_dll\msw mkdir ..\..\lib\gcc_dll\msw
C:\DOCUME~1\ADMINI~1.OUT\LOCALS~1\Temp\make13044.sh: command not found: not [1]
if not exist ..\..\lib\gcc_dll\msw\wx mkdir ..\..\lib\gcc_dll\msw\wx
C:\DOCUME~1\ADMINI~1.OUT\LOCALS~1\Temp\make13044.sh: command not found: not [1]
if not exist ..\..\lib\gcc_dll\msw\wx mkdir ..\..\lib\gcc_dll\msw\wx
C:\DOCUME~1\ADMINI~1.OUT\LOCALS~1\Temp\make13045.sh: command not found: not [1]
if not exist ..\..\lib\gcc_dll\msw\wx\setup.h copy ..\..\include\wx\msw\setup.h ..\..\lib\gcc_dll\msw\wx\setup.h
C:\DOCUME~1\ADMINI~1.OUT\LOCALS~1\Temp\make13046.sh: command not found: not [1]
gcc -c -o gcc_mswdll\wxregex_regcomp.o -O2 -mthreads -DHAVE_W32API_H -I..\..\include -I..\..\lib\gcc_dll\msw -D__WXMSW
__ -MTgcc_mswdll\wxregex_regcomp.o -MFgcc_mswdll\wxregex_regcomp.o.d -MD ../../src/regex/regcomp.c
In file included from ../../include/wx/defs.h:21,
from ../../include/wx/wxchar.h:21,
from ../../src/regex/regcustom.h:39,
from ../../src/regex/regguts.h:38,
from ../../src/regex/regcomp.c:33:
../../include/wx/platform.h:190:22: wx/setup.h: No such file or directory
In file included from ../../include/wx/platform.h:258,
from ../../include/wx/defs.h:21,
from ../../include/wx/wxchar.h:21,
from ../../src/regex/regcustom.h:39,
from ../../src/regex/regguts.h:38,
from ../../src/regex/regcomp.c:33:
... etc, followed by a good dose of the now familiar:
../../include/wx/chkconf.h:84:9: #error "wxUSE_DYNLIB_CLASS must be defined."
../../include/wx/chkconf.h:92:9: #error "wxUSE_EXCEPTIONS must be defined."
../../include/wx/chkconf.h:100:9: #error "wxUSE_FILESYSTEM must be defined."
../../include/wx/chkconf.h:113:9: #error "wxUSE_DYNAMIC_LOADER must be defined."
../../include/wx/chkconf.h:121:9: #error "wxUSE_LOG must be defined."
../../include/wx/chkconf.h:129:9: #error "wxUSE_LONGLONG must be defined."
../../include/wx/chkconf.h:137:9: #error "wxUSE_MIMETYPE must be defined."
../../include/wx/chkconf.h:153:9: #error "wxUSE_PROTOCOL must be defined."
../../include/wx/chkconf.h:195:9: #error "wxUSE_REGEX must be defined."
../../include/wx/chkconf.h:203:9: #error "wxUSE_STDPATHS must be defined."
../../include/wx/chkconf.h:211:9: #error "wxUSE_XML must be defined."
../../include/wx/chkconf.h:219:9: #error "wxUSE_SOCKETS must be defined."
../../include/wx/chkconf.h:227:9: #error "wxUSE_STREAMS must be defined."
../../include/wx/chkconf.h:235:9: #error "wxUSE_STOPWATCH must be defined."
... etc, etc.
This implies to me that I have not given proper attention to the configuration of the build in some important way, such as by running configure. I got around all this the last time by using msys and running configure, and then running the build from the msys prompt. This despite the fact that everything in the recommended procedure (and install-msw.txt) seems to tell me *not* to do this. At least that way I was able to do a successful build and get the libraries and setup.h that I needed. Something seems to be seriously missing here. I am certain that whatever I am doing wrong seems too obvious to mention for old hands at this process. But it certainly has caused me an excess of grief.
as always, I am hoping someone can show me the error(s) of my ways.
thanks,
--dave
TDragon:
--- Quote from: wittend on February 24, 2006, 05:12:46 am ---This despite the fact that everything in the recommended procedure (and install-msw.txt) seems to tell me *not* to do this.
--- End quote ---
Indeed; the Windows downloads for wxWidgets come preconfigured with the correct makefiles to build everything, and do not require MSys or any traditional Unix shell utilities at all. Thus, two possibilities come to mind:
1. You have the wrong wxWidgets installation. Make sure it's wxMSW-2.6.2.zip, or wxWidgets-2.6.3-rc1.zip (I have successfully built and used both).
2. The make executable included with MSys is somehow interfering with the original mingw32-make, or mingw32-make or related files have been overwritten somehow.
Whatever the case, commands such as "if not exist" belong only in the Unix-style build system and are not used in the MSW build.
Of the two commands you posted, the second is entirely correct, although it will only clean the directory of output files; the second should be "mingw32-make" instead of the plain "make", and once corrected should perform the build. Sometimes it's the little things like that which trip you up, and all you can do is try again.
MortenMacFly:
--- Quote from: wittend on February 24, 2006, 05:12:46 am ---D:\bin\CodeBlocks\wx\build\msw>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean
--- End quote ---
Please note that unless you are really want a non-Unicode (for an ANSI build of C::B) build I would suggest that you do a UNICODE=1.
Furthermore, things I've noticed:
- Why do you have installed wxWidgets to D:\bin\CodeBlocks\wx? It doesn't belong to C::B so I would suggest a clear seperation, as e.g. a folder D:\bin\CodeBlocks\ for the C::B sources and D:\bin\wxWidgets\ for wxWidgets. This may avboid conflicts in directories.
- Did you verify that you don't have setup any PATH to conflicting compilers etc? Thus is you have a conflicting gcc/make/whatever program in the way such errors could be caused by that.
I've attached you a a batch file (Windows) that I personally use to compile wxWidgets 2.6.2 successully. You might want to give this a try. You should only have to setup th path's accordingly. Please note that in the batch file I'm using the compiler suite that ships with the RC2 of C::B. But this should also work if you install MinGW only (NOT MSYS!). You can also download the packages that are required from the MinGW webpage. I use:
- binutils-2.16.91-20060119-1.tar.gz
- gcc-core-3.4.5-20060117-1.tar.gz
- gcc-g++-3.4.5-20060117-1.tar.gz
- gcc-g77-3.4.5-20060117-1.tar.gz
- mingw-runtime-3.9.tar.gz
- mingw-utils-0.3.tar.gz
- mingw32-make-3.80.0-3.tar.gz
- w32api-3.6.tar.gz
- gdb-6.3-2_snapshot.zip
...simply extracted into ONE directory. This directory you would have to use with the batch file if you don't want to install RC2 with the compilers again. So replace "D:\Devel\CodeBlocks_RC2" with "D:\Devel\MinGW" in the batch file then.
Again: This batch file ensures no conflicts in the PATH which (for me) was important.
Good luck!
Morten.
[attachment deleted by admin]
Michael:
--- Quote from: TDragon on February 24, 2006, 06:24:29 am ---[...]Make sure it's wxMSW-2.6.2.zip, or wxWidgets-2.6.3-rc1.zip (I have successfully built and used both).
--- End quote ---
Did you build C::B with wxWidgets-2.6.3-rc1? If yes, did C::B looks as with wxWidgets-2.6.2? C::B gives me some layout problems with wxWidgets-2.6.3-rc1.
Best wishes,
Michael
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version