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 GNU make which is part of
15 part of the CygWin32 toolchain and is also available as
16 a stand alone port without the infamous Cygwin.dll from
18 http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32
20 The makefile has small problems with Cygwin´s tools
21 so it is recommended not to use these (but MingGW32
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
33 #define wxUSE_SOCKETS 0
35 #define wxUSE_THREADS 1
36 #define wxUSE_FS_INET 0
37 #define wxUSE_FS_ZIP 1
38 #define wxUSE_BUSYINFO 1
39 #define wxUSE_DYNLIB_CLASS 1
40 #define wxUSE_ZIPSTREAM 1
41 #define wxUSE_LIBJPEG 1
42 #define wxUSE_LIBPNG 1
44 and iostreams ares disabled with
45 #define wxUSE_STD_IOSTREAM 0
46 -> type: cd c:\wxWin\src\msw
47 -> type: make -f makefile.g95
52 Building wxGTK or wxMotif completely without configure
53 won't ever work, but there is now a new makefile system
54 that works without libtool and automake, using only
55 configure to create what is needed.
57 Set WXWIN environment variable to the base directory such
58 as ~/wxWindows (this is actually not really needed).
60 -> type: export WXWIN=~/wxWindows
63 -> type: ../configure --with-motif
64 or type: ../configure --with-gtk
66 -> type: su <type root password>
71 Call configure with --disable-shared to create a static
72 library. Calling "make uninstall" will remove the installed
73 library and "make dist" will create a distribution (not
76 III) Windows using configure
77 ----------------------------------------
79 Take a look at Unix->Windows cross compiling. With minor
80 modifications, this should work in Windows if you've got the cygnus
81 utilities (bash, GNU make, etc) and either mingw32 or cygwin32 installed.
82 See http://www.cygnus.com for these programs, or go straight to their
83 ftp server at ftp://sourceware.cygnus.com/pub/cygwin/.
85 Of course, you can also build the library using plain makefiles (see
89 ----------------------------------------
92 ----------------------------------------
94 VII) Unix->Windows cross-compiling using configure
95 --------------------------------------------------
97 First you'll need a cross-compiler; linux glibc binaries of mingw32 and
98 cygwin32 (both based on egcs) can be found at
99 ftp://ftp.objsw.com/pub/crossgcc/linux-x-win32. Otherwise you can
100 compile one yourself. Check the relevant FAQs.
102 [ A Note about cygwin32 and mingw32: the main difference is that cygwin32
103 binaries are always linked against cygwin.dll. This dll encapsulates most
104 standard Unix C extensions, which is very handy if you're porting unix
105 software to windows. However, wxMSW doesn't need this, so mingw32 is
106 preferable if you write portable C(++). ]
108 You might want to build both Unix and Windows binaries in the same source
109 tree; to do this make subdirs for each e.g. unix and win32. If you've
110 already build wxWindows in the main dir, do a 'make distclean' there,
111 otherwise configure will get confused. (In any case, read the section 'Unix
112 using configure' and make sure you're able to build a native wxWindows
113 library; cross-compiling errors can be pretty obscure and you'll want to be
114 sure that your configure setup is basically sound.)
116 To cross compile the windows library, do
118 (or whatever you called it)
119 Now run configure. There are two ways to do this
120 -> ../configure --host=i586-mingw32 --build=i586-linux --with-mingw \
122 where --build= should read whatever platform you're building on. Configure
123 will notice that build and host platforms differ, and automatically prepend
124 i586-mingw32- to gcc, ar, ld, etc (make sure they're in the PATH!).
125 The other way to run configure is by specifying the names of the binaries
127 -> CC=i586-mingw32-gcc CXX=i586-mingw32-g++ RANLIB=i586-mingw32-ranlib \
128 DLLTOOL=i586-mingw32-dlltool LD=i586-mingw32-ld NM=i586-mingw32-nm \
129 ../configure --host=i586-mingw32 --with-mingw --enable-dnd=no
131 (all assuming you're using mingw32)
132 Drag'n'drop is disabled because mingw32 lacks (AFAIK) OLE headers.
134 [ Update: some new mingw32 versions now have a new set of windows header
135 files, which apparently can handle ole. Untested at the moment ]
137 Configure will conclude that shared libraries are out of the question and
138 opt for a static one. I haven't looked into DLL creation yet.
142 and wait, wait, wait. Don't leave the room, because the minute you do there
143 will be a compile error :-)
145 If this is successful, you end up with a libwx_msw.a in win32/lib. Now try
146 building the minimal sample:
148 -> cd samples/minimal
150 -> mv minimal minimal.exe
152 and run it with wine, for example
155 If all is well, do an install; from win32
158 Native and cross-compiled installations can co-exist peacefully
159 (as long as their widget sets differ), except for wx-config. You might
160 want to rename the cross-compiled one to i586-mingw32-wx-config, or something.
162 Cross-compiling TODO:
163 ---------------------
164 - resource compiling must be done manually for now (should/can we link the
165 default wx resources into libwx_msw.a?) [ No we can't; the linker won't
166 link it in... you have to supply an object file ]
168 - static executables are HUGE -- there must be room for improvement.