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