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
  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: make
  67 -> type: su <type root password>
  68 -> type: make install
  69 -> type: ldconfig
  70 -> type: exit
  71
  72 III) Windows using configure
  73 ----------------------------------------
  74
  75 Take a look at Unix->Windows cross compiling. With minor
  76 modifications, this should work in Windows if you've got the cygnus
  77 utilities (bash, GNU make, etc) and either mingw32 or cygwin32 installed.
  78 See http://www.cygnus.com for these programs, or go straight to their
  79 ftp server at ftp://sourceware.cygnus.com/pub/cygwin/.
  80
  81 Of course, you can also build the library using plain makefiles (see
  82 section I).
  83
  84 V) MacOS
  85 ----------------------------------------
  86
  87 VI) OS/2
  88 ----------------------------------------
  89
  90 VII) Unix->Windows cross-compiling using configure
  91 --------------------------------------------------
  92
  93 First you'll need a cross-compiler; linux glibc binaries of mingw32 and
  94 cygwin32 (both based on egcs) can be found at
  95 ftp://ftp.objsw.com/pub/crossgcc/linux-x-win32. Otherwise you can
  96 compile one yourself. Check the relevant FAQs.
  97
  98 [ A Note about cygwin32 and mingw32: the main difference is that cygwin32
  99 binaries are always linked against cygwin.dll. This dll encapsulates most
 100 standard Unix C extensions, which is very handy if you're porting unix
 101 software to windows. However, wxMSW doesn't need this, so mingw32 is
 102 preferable if you write portable C(++). ]
 103
 104 You might want to build both Unix and Windows binaries in the same source
 105 tree; to do this make subdirs for each e.g. unix and win32. If you've
 106 already build wxWindows in the main dir, do a 'make distclean' there,
 107 otherwise configure will get confused. (In any case, read the section 'Unix
 108 using configure' and make sure you're able to build a native wxWindows
 109 library; cross-compiling errors can be pretty obscure and you'll want to be
 110 sure that your configure setup is basically sound.)
 111
 112 To cross compile the windows library, do
 113 -> cd win32
 114 Now run configure. There are two ways to do this
 115 -> ../configure --host=i586-mingw32 --build=i586-linux --with-mingw \
 116    --enable-dnd=no
 117 where --build= should read whatever platform you're building on. Configure
 118 will notice that build and host platforms differ, and automatically prepend
 119 i586-mingw32- to gcc, ar, ld, etc (make sure they're in the PATH!).
 120 The other way to run configure is by specifying the names of the binaries
 121 yourself:
 122 -> CC=i586-mingw32-gcc CXX=i586-mingw32-g++ RANLIB=i586-mingw32-ranlib \
 123    DLLTOOL=i586-mingw32-dlltool LD=i586-mingw32-ld NM=i586-mingw32-nm \
 124    ../configure --host=i586-mingw32 --with-mingw --enable-dnd=no
 125
 126 (all assuming you're using mingw32)
 127 Drag'n'drop is disabled because mingw32 lacks (AFAIK) OLE headers.
 128
 129 Configure will conclude that shared libraries are out of the question and
 130 opt for a static one. I haven't looked into DLL creation yet.
 131
 132 Type
 133 -> make -C src
 134 and wait, wait, wait. Don't leave the room, because the minute you do there
 135 will be a compile error :-)
 136
 137 If this is successful, try building the minimal sample:
 138 -> cd samples/minimal
 139 -> make
 140 -> mv minimal minimal.exe
 141
 142 and run it with wine, for example
 143 -> wine minimal.exe
 144
 145 If all is well, do an install; from win32
 146 -> make install
 147
 148 Native and cross-compiled installations can co-exist peacefully
 149 (as long as their widget sets differ), except for wx-config. You might
 150 want to rename the cross-compiled one to i586-mingw32-wx-config, or something.
 151
 152 Cross-compiling TODO:
 153 ---------------------
 154 - resource compiling must be done manually for now (should/can we link the
 155 default wx resources into libwx_msw.a?) [ No we can't; the linker won't
 156 link it in... you have to supply an object file ]
 157 - dynamic libraries
 158 - static executables are HUGE -- there must be room for improvement.
 159