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.
  56
  57 In order to create configure, you need to have the
  58 GNU autoconf package (version 2.13 or 2.14) installed
  59 on your system and type run "autoconf" in the base
  60 directory (or run the autogen.sh script in the same
  61 directory, which just calls autoconf).
  62
  63 Set WXWIN environment variable to the base directory such
  64 as ~/wxWindows (this is actually not really needed).
  65
  66 -> type: export WXWIN=~/wxWindows
  67 -> type: md mybuild
  68 -> type: cd mybuild
  69 -> type: ../configure --with-motif
  70 or type: ../configure --with-gtk
  71 -> type: make
  72 -> type: su <type root password>
  73 -> type: make install
  74 -> type: ldconfig
  75 -> type: exit
  76
  77 Call configure with --disable-shared to create a static
  78 library. Calling "make uninstall" will remove the installed
  79 library and "make dist" will create a distribution (not
  80 yet complete).
  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 V) MacOS
  95 ----------------------------------------
  96
  97 VI) OS/2
  98 ----------------------------------------
  99
 100 VII) Unix->Windows cross-compiling using configure
 101 --------------------------------------------------
 102
 103 First you'll need a cross-compiler; linux glibc binaries of mingw32 and
 104 cygwin32 (both based on egcs) can be found at
 105 ftp://ftp.objsw.com/pub/crossgcc/linux-x-win32. Otherwise you can
 106 compile one yourself. Check the relevant FAQs.
 107
 108 [ A Note about cygwin32 and mingw32: the main difference is that cygwin32
 109 binaries are always linked against cygwin.dll. This dll encapsulates most
 110 standard Unix C extensions, which is very handy if you're porting unix
 111 software to windows. However, wxMSW doesn't need this, so mingw32 is
 112 preferable if you write portable C(++). ]
 113
 114 You might want to build both Unix and Windows binaries in the same source
 115 tree; to do this make subdirs for each e.g. unix and win32. If you've
 116 already build wxWindows in the main dir, do a 'make distclean' there,
 117 otherwise configure will get confused. (In any case, read the section 'Unix
 118 using configure' and make sure you're able to build a native wxWindows
 119 library; cross-compiling errors can be pretty obscure and you'll want to be
 120 sure that your configure setup is basically sound.)
 121
 122 To cross compile the windows library, do
 123 -> cd win32
 124 Now run configure. There are two ways to do this
 125 -> ../configure --host=i586-mingw32 --build=i586-linux --with-mingw \
 126    --enable-dnd=no
 127 where --build= should read whatever platform you're building on. Configure
 128 will notice that build and host platforms differ, and automatically prepend
 129 i586-mingw32- to gcc, ar, ld, etc (make sure they're in the PATH!).
 130 The other way to run configure is by specifying the names of the binaries
 131 yourself:
 132 -> CC=i586-mingw32-gcc CXX=i586-mingw32-g++ RANLIB=i586-mingw32-ranlib \
 133    DLLTOOL=i586-mingw32-dlltool LD=i586-mingw32-ld NM=i586-mingw32-nm \
 134    ../configure --host=i586-mingw32 --with-mingw --enable-dnd=no
 135
 136 (all assuming you're using mingw32)
 137 Drag'n'drop is disabled because mingw32 lacks (AFAIK) OLE headers.
 138
 139 Configure will conclude that shared libraries are out of the question and
 140 opt for a static one. I haven't looked into DLL creation yet.
 141
 142 Type
 143 -> make -C src
 144 and wait, wait, wait. Don't leave the room, because the minute you do there
 145 will be a compile error :-)
 146
 147 If this is successful, try building the minimal sample:
 148 -> cd samples/minimal
 149 -> make
 150 -> mv minimal minimal.exe
 151
 152 and run it with wine, for example
 153 -> wine minimal.exe
 154
 155 If all is well, do an install; from win32
 156 -> make install
 157
 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.
 161
 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 ]
 167 - dynamic libraries
 168 - static executables are HUGE -- there must be room for improvement.
 169