BuildCVS.txt

   1 ------------------------------------------------------------------------
   2                 How to build the sources from CVS
   3 ------------------------------------------------------------------------
   4
   5 I) Windows using plain makefiles
   6 ----------------------------------------
   7
   8 a) Using the GNU MinGW32 or GNU CygWin32 compilers
   9
  10 You'll need the compiler itself which is available from
  11
  12   http://www.cygwin.com
  13
  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
  17
  18   http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32
  19
  20 The makefile has small problems with Cygwin´s tools
  21 so it is recommended not to use these (but MingGW32
  22 and its make.exe).
  23
  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
  27    into c:\wxWin
  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       0
  33    #define wxUSE_HTML          1
  34    #define wxUSE_THREADS       1
  35    #define wxUSE_FS_INET       0
  36    #define wxUSE_FS_ZIP        1
  37    #define wxUSE_BUSYINFO      1
  38    #define wxUSE_DYNLIB_CLASS  1
  39    #define wxUSE_ZIPSTREAM     1
  40    #define wxUSE_JPEGLIB       1
  41    #define wxUSE_PNGLIB        1
  42
  43    and iostreams ares disabled with
  44    #define wxUSE_STD_IOSTREAM   0
  45 -> type: cd c:\wxWin\src\msw
  46 -> type: make -f makefile.g95
  47
  48 II) Unix ports using plain makefiles.
  49 --------------------------------------
  50
  51 Building wxGTK or wxMotif completely without configure
  52 won't ever work, but there is now a new makefile system
  53 that works without libtool and automake, using only
  54 configure to create what is needed. So far, no shared
  55 libraries can be build with this system.
  56
  57 Set WXWIN environment variable to the base directory such
  58 as ~/wxWindows (this is actually not really needed).
  59
  60 -> type: export WXWIN=~/wxWindows
  61 -> type: md mybuild
  62 -> type: cd mybuild
  63 -> type: ../configure --with-motif
  64 or type: ../configure --with-gtk
  65 -> type: cd src/gtk
  66 or type: cd src/motif
  67 -> type: make -f makefile.unx
  68
  69
  70 III) Windows using configure
  71 ----------------------------------------
  72
  73 Take a look at Unix->Windows cross compiling. With minor
  74 modifications, this should work in Windows if you've got the cygnus
  75 utilities (bash, GNU make, etc) and either mingw32 or cygwin32 installed.
  76 See http://www.cygnus.com for these programs, or go straight to their
  77 ftp server at ftp://sourceware.cygnus.com/pub/cygwin/.
  78
  79 Of course, you can also build the library using plain makefiles (see
  80 section I).
  81
  82 IV) Unix using configure
  83 ----------------------------------------
  84
  85 a) You have all the newest and greatest GNU tools installed on your system
  86 and in the same directory hierachy (e.g. either all tools in /usr or all
  87 in /usr/local), these tools are:
  88 - GNU libtool 1.2e (1.3 doesn't work here)
  89 - GNU autoconf 2.13 (including autoheader 2.13)
  90 - GNU automake 1.4 (including aclocal 1.4)
  91 and possibly but not forcibly
  92 - GNU make 3.76.1
  93 - GNU C++ (EGCS)
  94
  95 -> Go to the base directory
  96 -> type: ./autogen.sh
  97
  98 b) You don't know what autos are and have no driver's licence anyway:
  99
 100 -> Go to the testconf directory
 101 -> type: ./apply
 102
 103 a+b) Then proceed in either case with:
 104
 105 -> Choose a directory name that seems fit for building wxWindows, e.g. mybuild
 106 -> Go the base directory
 107 -> type: mkdir mybuild
 108 -> type: cd mybuild
 109 -> type: ../configure --with-gtk
 110 or type: ../configure --with-motif
 111 or type: ../configure --with-wine
 112 -> type make
 113 -> drink lots of coffee and go shopping
 114
 115
 116 V) MacOS
 117 ----------------------------------------
 118
 119 VI) OS/2
 120 ----------------------------------------
 121
 122 VII) Unix->Windows cross-compiling using configure
 123 --------------------------------------------------
 124
 125 First you'll need a cross-compiler; linux glibc binaries of mingw32 and
 126 cygwin32 (both based on egcs) can be found at
 127 ftp://ftp.objsw.com/pub/crossgcc/linux-x-win32. Otherwise you can
 128 compile one yourself. Check the relevant FAQs.
 129
 130 [ A Note about cygwin32 and mingw32: the main difference is that cygwin32
 131 binaries are always linked against cygwin.dll. This dll encapsulates most
 132 standard Unix C extensions, which is very handy if you're porting unix
 133 software to windows. However, wxMSW doesn't need this, so mingw32 is
 134 preferable if you write portable C(++). ]
 135
 136 You might want to build both Unix and Windows binaries in the same source
 137 tree; to do this make subdirs for each e.g. unix and win32. If you've
 138 already build wxWindows in the main dir, do a 'make distclean' there,
 139 otherwise configure will get confused. (In any case, read the section 'Unix
 140 using configure' and make sure you're able to build a native wxWindows
 141 library; cross-compiling errors can be pretty obscure and you'll want to be
 142 sure that your configure setup is basically sound.)
 143
 144 To cross compile the windows library, do
 145 -> cd win32
 146 Now run configure. There are two ways to do this
 147 -> ../configure --host=i586-mingw32 --build=i586-linux --with-mingw \
 148    --enable-dnd=no
 149 where --build= should read whatever platform you're building on. Configure
 150 will notice that build and host platforms differ, and automatically prepend
 151 i586-mingw32- to gcc, ar, ld, etc (make sure they're in the PATH!).
 152 The other way to run configure is by specifying the names of the binaries
 153 yourself:
 154 -> CC=i586-mingw32-gcc CXX=i586-mingw32-g++ RANLIB=i586-mingw32-ranlib \
 155    DLLTOOL=i586-mingw32-dlltool LD=i586-mingw32-ld NM=i586-mingw32-nm \
 156    ../configure --host=i586-mingw32 --with-mingw --enable-dnd=no
 157
 158 (all assuming you're using mingw32)
 159 Drag'n'drop is disabled because mingw32 lacks (AFAIK) OLE headers.
 160
 161 Configure will conclude that shared libraries are out of the question and
 162 opt for a static one. I haven't looked into DLL creation yet.
 163
 164 Type
 165 -> make -C src
 166 and wait, wait, wait. Don't leave the room, because the minute you do there
 167 will be a compile error :-)
 168
 169 If this is successful, try building the minimal sample:
 170 -> cd samples/minimal
 171 -> make
 172 -> mv minimal minimal.exe
 173
 174 and run it with wine, for example
 175 -> wine minimal.exe
 176
 177 If all is well, do an install; from win32
 178 -> make install
 179
 180 Native and cross-compiled installations can co-exist peacefully
 181 (as long as their widget sets differ), except for wx-config. You might
 182 want to rename the cross-compiled one to i586-mingw32-wx-config, or something.
 183
 184 Cross-compiling TODO:
 185 ---------------------
 186 - resource compiling must be done manually for now (should/can we link the
 187 default wx resources into libwx_msw.a?) [ No we can't; the linker won't
 188 link it in... you have to supply an object file ]
 189 - dynamic libraries
 190 - static executables are HUGE -- there must be room for improvement.
 191