1 ------------------------------------------------------------------------
2 How to build the sources from CVS
3 ------------------------------------------------------------------------
5 I) Windows using plain makefiles
6 ----------------------------------------
8 a) Using the GNU MingW32 or GNU Cygwin32 compilers
10 You'll need the compiler itself which is available from
14 When using MingW32 you'll need a few of the tools that
15 are either shipped separately or only as part of the
16 Cygwin32 toolchain. First and foremost, you'll need
21 make.exe is also available from
22 http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32
24 -> Set your path so that it includes the directory
25 where your compiler and tools reside
26 -> Assume that you installed the wxWindows sources
28 -> Copy c:\wxWin\include\wx\msw\setup0.h
29 to c:\wxWin\include\wx\msw\setup.h
30 -> Edit c:\wxWin\include\wx\msw\setup.h so that
31 most features are enabled (i.e. defined to 1) with
32 #define wxUSE_SOCKETS 1
34 #define wxUSE_THREADS 1
35 #define wxUSE_FS_INET 1
36 #define wxUSE_FS_ZIP 1
37 #define wxUSE_BUSYINFO 1
38 #define wxUSE_DYNLIB_CLASS 1
39 #define wxUSE_ZIPSTREAM 1
41 and disbale iostreams with
42 #define wxUSE_STD_IOSTREAM 0
43 -> type: cd c:\wxWin\src\msw
44 -> type: make -f makefile.g95
46 II) Unix using plain makefiles.
47 ----------------------------------------
49 Set WXWIN environment variable to the base directory such
52 -> type: export WXWIN=~/wxWindows
54 Edit ~/wxWindows/src/make.env as you wish.
55 -> type: cd ~/wxWindows/src/gtk
56 -> type: cp ./setup0.h setup.h
57 -> type: make -f makefile.unx gtk
60 III) Windows using configure
61 ----------------------------------------
63 No idea.., but take a look at Unix->Windows cross compiling. With minor
64 modifications, this should work in Windows if you've got the cygnus
65 utilities (bash, GNU make, etc) and either mingw32 or cygwin32 installed.
66 See http://www.cygnus.com for these programs.
68 IV) Unix using configure
69 ----------------------------------------
71 a) You have all the newest and greatest GNU tools installed on your system
72 and in the same directory hierachy (e.g. either all tools in /usr or all
73 in /usr/local), these tools are:
74 - GNU libtool 1.2e (1.3 doesn't work here)
75 - GNU autoconf 2.13 (including autoheader 2.13)
76 - GNU automake 1.4 (including aclocal 1.4)
77 and possibly but not forcibly
81 -> Go to the base directory
84 b) You don't know what autos are and have no driver's licence anyway:
86 -> Go to the testconf directory
89 a+b) Then proceed in either case with:
91 -> Choose a directory name that seems fit for building wxWindows, e.g. mybuild
92 -> Go the base directory
93 -> type: mkdir mybuild
95 -> type: ../configure --with-gtk
96 or type: ../configure --with-motif
97 or type: ../configure --with-wine
99 -> drink lots of coffee and go shopping
103 ----------------------------------------
106 ----------------------------------------
108 VII) Unix->Windows cross-compiling using configure
109 --------------------------------------------------
111 First you'll need a cross-compiler; linux glibc binaries of mingw32 and
112 cygwin32 (both based on egcs) can be found at
113 ftp://ftp.objsw.com/pub/crossgcc/linux-x-win32. Otherwise you can
114 compile one yourself. Check the relevant FAQs.
116 [ A Note about cygwin32 and mingw32: the main difference is that cygwin32
117 binaries are always linked against cygwin.dll. This dll encapsulates most
118 standard Unix C extensions, which is very handy if you're porting unix
119 software to windows. However, wxMSW doesn't need this, so mingw32 is
120 preferable if you write portable C(++). ]
122 You might want to build both Unix and Windows binaries in the same source
123 tree; to do this make subdirs for each e.g. unix and win32. If you've
124 already build wxWindows in the main dir, do a 'make distclean' there,
125 otherwise configure will get confused. (In any case, read the section 'Unix
126 using configure' and make sure you're able to build a native wxWindows
127 library; cross-compiling errors can be pretty obscure and you'll want to be
128 sure that your configure setup is basically sound.)
130 To cross compile the windows library, do
132 -> CC=i586-mingw32-gcc CXX=i586-mingw32-g++ RANLIB=i586-mingw32-ranlib \
133 DLLTOOL=i586-mingw32-dlltool LD=i586-mingw32-ld NM=i586-mingw32-nm \
134 ../configure --host=i586-mingw32 --with-mingw --enable-dnd=no
136 (assuming you're using mingw32)
138 The important thing to notice here is that we suply configure with the names
139 of all the non-default binutils (make sure they're in the PATH!), and that
140 we tell configure to build for the host platform i586-mingw32.
141 Drag'n'drop is disabled because mingw32 lacks (AFAIK) OLE headers.
143 Configure will conclude that shared libraries are out of the question and
144 opt for a static one. I haven't looked into DLL creation yet.
146 When configure is finished, examine setup.h in the win32 directory. Search for
147 wxUSE_DYNLIB_CLASS, it will be defined twice. Remove the second define (0).
148 If your cross-compiler is egcs-based, you might want to add #define __EGCS__
149 in setup.h (only used by common/timercmn.cpp).
153 and wait, wait, wait. Don't leave the room, because the minute you do there
154 will be a compile error :-)
156 If this is successful, try building the minimal sample:
157 -> cd samples/minimal
159 -> mv minimal minimal.exe
161 and run it with wine, for example
164 If all is well, do an install; from win32
167 Native and cross-compiled installations can co-exist peacefully
168 (as long as their widget sets differ), except for wx-config. You might
169 want to rename the cross-compiled one to i586-mingw32-wx-config, or something.
171 Cross-compiling TODO:
172 ---------------------
173 - resource compiling must be done manually for now (should/can we link the
174 default wx resources into libwx_msw.a?)
176 - static executables are HUGE -- there must be room for improvement.
177 - wxUSE_DYNLIB_CLASS double def is probably a bug in configure.in
178 - figure out a clean way to determine we're building with configure
179 - possibly some problems with parser.y and lexer.c and the like.