1
------------------------------------------------------------------------
2
How to build the sources from SVN
3
------------------------------------------------------------------------
5
Please use the install.txt files in docs/gtk, docs/msw, docs/motif, docs/mac
6
etc. alongside these instructions.
8
I) Windows using plain makefiles
9
----------------------------------------
11
a) If using Microsoft Visual C++ 5.0 or 6.0
13
Ensure that the command-line compiler and tools (including
14
nmake) are installed and ready to run. Depending on your
15
installation there may be a batch file (commonly named VCVARS32.BAT)
16
that needs to be run to set correct environment variables and PATH entries.
18
Continue with item c) below.
21
b) If using the MinGW or Cygwin compilers
23
You can get MinGW from http://www.mingw.org/
25
Cygwin is available at http://www.cygwin.com/
27
If you are using Cygwin or MinGW together with the MSYS environment, you
28
can build the library using configure (see "Unix ports" and
29
"Windows using configure" below). You can also
30
build wxWidgets without configure using native makefile, but only with
31
MinGW. Using Cygwin together with Windows makefile is no longer supported.
33
If building with MinGW without configure:
35
-> Set your path so that it includes the directory
36
where your compiler and tools reside
38
-> Make sure you have GNU Make installed. It must be Windows native version.
39
Download it from http://www.mingw.org, the executable will be called
42
-> Modern version of MinGW is required; preferably MinGW 2.0 (with gcc3),
43
but MinGW with gcc-2.95.3 will suffice. If you are using 2.95, you will
44
have to change variable GCC_VERSION in config.gcc (see msw/install.txt
47
If using configure, Unix instructions apply.
52
Assuming that you installed the wxWidgets sources into c:\wxWidgets:
54
-> Copy c:\wxWidgets\include\wx\msw\setup0.h
55
to c:\wxWidgets\include\wx\msw\setup.h
56
-> Edit c:\wxWidgets\include\wx\msw\setup.h to choose
57
the features you would like to compile wxWidgets with[out].
59
and std iostreams are disabled with
60
#define wxUSE_STD_IOSTREAM 0
62
-> type: cd c:\wxWidgets\build\msw
63
-> type: make -f makefile.gcc (if using GNU tools)
64
or type: nmake -f makefile.vc (if using MS VC++)
67
See also docs/msw/install.txt for additional compilation options.
69
d) Borland (including free command line tools)
70
Download tools from http://www.borland.com/downloads/
72
See docs/msw/install.txt for details; in brief:
74
-> type cd c:\wxWidgets\build\msw
75
-> type make -f makefile.bcc
77
You can customize many things in the build process, detailed description is
78
in docs/msw/install.txt.
84
Building wxGTK or wxMotif completely without configure
85
won't ever work, but there is now a new makefile system
86
that works without libtool and automake, using only
87
configure to create what is needed.
89
In order to create configure, you need to have the
90
GNU autoconf package (version > 2.54) installed
91
on your system and type run "autoconf" in the base
92
directory (or run the autogen.sh script in the same
93
directory, which just calls autoconf). Note that you usually don't
94
need to do this because configure is included in SVN.
96
Set WXWIN environment variable to the base directory such
97
as ~/wxWidgets (this is actually not really needed).
99
-> type: export WXWIN=~/wxWidgets
102
-> type: ../configure --with-motif
103
or type: ../configure --with-gtk
105
-> type: su <type root password>
106
-> type: make install
110
Call configure with --disable-shared to create a static
111
library. Calling "make uninstall" will remove the installed
112
library and "make dist" will create a distribution (not
115
III) Windows using configure
116
----------------------------------------
118
wxWidgets can be built on Windows using MSYS (see
119
http://www.mingw.org/), which is a POSIX build environment
120
for Windows. With MSYS you can just ./configure && make (see also VII,
121
Unix->Windows cross-compiling using configure).
123
Of course, you can also build the library using plain makefiles (see
126
V) MacOS X using configure and the Developer Tools
127
----------------------------------------
129
You need to have the Developer Tools installed. If this is not the case,
130
you will need to register at the Apple Developer web site (this is a free
131
registration) in order to download the Developer Tools installer.
133
In order to create configure, you need to have the
134
GNU autoconf package (version >= 2.54) installed
135
on your system and type run "autoconf" in the base
136
directory (or run the autogen.sh script in the same
137
directory, which just calls autoconf).
139
-> type: mkdir macbuild
141
-> type: ../configure --with-mac
142
or type: ../configure
146
----------------------------------------
149
VII) Unix->Windows cross-compiling using configure
150
--------------------------------------------------
152
First you'll need a cross-compiler; linux glibc binaries of MinGW and
153
Cygwin (both based on egcs) can be found at
154
ftp://ftp.objsw.com/pub/crossgcc/linux-x-win32. Alternative binaries,
155
based on the latest MinGW release can be found at
156
http://members.telering.at/jessich/mingw/mingwcross/mingw_cross.html
157
Otherwise you can compile one yourself.
159
[ A Note about Cygwin and MinGW: the main difference is that Cygwin
160
binaries are always linked against cygwin.dll. This dll encapsulates most
161
standard Unix C extensions, which is very handy if you're porting unix
162
software to windows. However, wxMSW doesn't need this, so MinGW is
163
preferable if you write portable C(++). ]
165
You might want to build both Unix and Windows binaries in the same source
166
tree; to do this make subdirs for each e.g. unix and win32. If you've
167
already build wxWidgets in the main dir, do a 'make distclean' there,
168
otherwise configure will get confused. (In any case, read the section 'Unix
169
using configure' and make sure you're able to build a native wxWidgets
170
library; cross-compiling errors can be pretty obscure and you'll want to be
171
sure that your configure setup is basically sound.)
173
To cross compile the windows library, do
175
(or whatever you called it)
176
Now run configure. There are two ways to do this
177
-> ../configure --host=i586-mingw32 --build=i586-linux --with-mingw
178
where --build= should read whatever platform you're building on. Configure
179
will notice that build and host platforms differ, and automatically prepend
180
i586-mingw32- to gcc, ar, ld, etc (make sure they're in the PATH!).
181
The other way to run configure is by specifying the names of the binaries
183
-> CC=i586-mingw32-gcc CXX=i586-mingw32-g++ RANLIB=i586-mingw32-ranlib \
184
DLLTOOL=i586-mingw32-dlltool LD=i586-mingw32-ld NM=i586-mingw32-nm \
185
../configure --host=i586-mingw32 --with-mingw
187
(all assuming you're using MinGW)
188
By default this will compile a DLL, if you want a static library,
189
specify --disable-shared.
193
and wait, wait, wait. Don't leave the room, because the minute you do there
194
will be a compile error :-)
196
NB: if you are using a very old compiler you risk to get quite a few warnings
197
about "ANSI C++ forbids implicit conversion from 'void *'" in all places
198
where va_arg macro is used. This is due to a bug in (some versions of)
199
MinGW headers which may be corrected by upgrading your compier,
200
otherwise you might edit the file
202
${install_prefix}/lib/gcc-lib/i586-mingw32/egcs-2.91.57/include/stdarg.h
204
(instead of egcs-2.91.57 you may have something different), searching for
207
/* Define __gnuc_va_list. */
209
#ifndef __GNUC_VA_LIST
210
#define __GNUC_VA_LIST
211
#if defined(__svr4__) || defined(_AIX) || defined(_M_UNIX) || defined(__NetBSD__)
212
typedef char *__gnuc_va_list;
214
typedef void *__gnuc_va_list;
218
and adding "|| defined(_WIN32)" to the list of platforms on which
219
__gnuc_va_list is char *.
221
If this is successful, you end up with a wx23_2.dll/libwx23_2.a in win32/lib
222
(or just libwx_msw.a if you opted for a static build).
223
Now try building the minimal sample:
225
-> cd samples/minimal
228
and run it with wine, for example (or copy to a Windows box)
231
If all is well, do an install; from win32
234
Native and cross-compiled installations can co-exist peacefully
235
(as long as their widget sets differ), except for wx-config. You might
236
want to rename the cross-compiled one to i586-mingw32-wx-config, or something.
238
Cross-compiling TODO:
239
---------------------
240
- resource compiling must be done manually for now (should/can we link the
241
default wx resources into libwx_msw.a?) [ No we can't; the linker won't
242
link it in... you have to supply an object file ]
243
- static executables are HUGE -- there must be room for improvement.