Convert argv[] to Unicode

[wxWidgets.git] / BuildCVS.txt

diff --git a/BuildCVS.txt b/BuildCVS.txt
index 0622a9dfc1a40c2ec47152543d579fc2469c14ce..0feea2c139b38011b60c7e2d9c46d0270ba2df8c 100644 (file)
--- a/BuildCVS.txt
+++ b/BuildCVS.txt
@@ -5,8 +5,39 @@
 I) Windows using plain makefiles
 ----------------------------------------
 
 I) Windows using plain makefiles
 ----------------------------------------
 

-No idea, never did it.
-
+a) Using the GNU MinGW32 or GNU CygWin32 compilers
+
+You'll need the compiler itself which is available from
+
+  http://www.cygwin.com
+
+When using MingW32 you'll need GNU make which is part of
+part of the CygWin32 toolchain and is also available as
+a stand alone port without the infamous Cygwin.dll from
+
+  http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32
+
+-> Set your path so that it includes the directory
+   where your compiler and tools reside
+-> Assume that you installed the wxWindows sources
+   into c:\wxWin
+-> Copy c:\wxWin\include\wx\msw\setup0.h 
+   to   c:\wxWin\include\wx\msw\setup.h
+-> Edit c:\wxWin\include\wx\msw\setup.h so that
+   most features are enabled (i.e. defined to 1) with
+   #define wxUSE_SOCKETS       1
+   #define wxUSE_HTML          1
+   #define wxUSE_THREADS       1
+   #define wxUSE_FS_INET       1
+   #define wxUSE_FS_ZIP        1
+   #define wxUSE_BUSYINFO      1
+   #define wxUSE_DYNLIB_CLASS  1
+   #define wxUSE_ZIPSTREAM     1
+
+   and disbale iostreams with
+   #define wxUSE_STD_IOSTREAM   0
+-> type: cd c:\wxWin\src\msw
+-> type: make -f makefile.g95

 
 II) Unix using plain makefiles.
 ----------------------------------------
 
 II) Unix using plain makefiles.
 ----------------------------------------


@@ -25,10 +56,14 @@ Edit ~/wxWindows/src/make.env as you wish.
 III) Windows using configure
 ----------------------------------------
 
 III) Windows using configure
 ----------------------------------------
 

-No idea.., but take a look at Unix->Windows cross compiling. With minor
+Take a look at Unix->Windows cross compiling. With minor

 modifications, this should work in Windows if you've got the cygnus
 utilities (bash, GNU make, etc) and either mingw32 or cygwin32 installed. 
 modifications, this should work in Windows if you've got the cygnus
 utilities (bash, GNU make, etc) and either mingw32 or cygwin32 installed. 

-See http://www.cygnus.com for these programs.
+See http://www.cygnus.com for these programs, or go straight to their
+ftp server at ftp://sourceware.cygnus.com/pub/cygwin/. 
+
+Of course, you can also build the library using plain makefiles (see 
+section I).

 
 IV) Unix using configure
 ----------------------------------------
 
 IV) Unix using configure
 ----------------------------------------


@@ -94,25 +129,24 @@ sure that your configure setup is basically sound.)
 
 To cross compile the windows library, do
 -> cd win32
 
 To cross compile the windows library, do
 -> cd win32

+Now run configure. There are two ways to do this
+-> ../configure --host=i586-mingw32 --build=i586-linux --with-mingw \
+   --enable-dnd=no
+where --build= should read whatever platform you're building on. Configure
+will notice that build and host platforms differ, and automatically prepend
+i586-mingw32- to gcc, ar, ld, etc (make sure they're in the PATH!). 
+The other way to run configure is by specifying the names of the binaries 
+yourself:

 -> CC=i586-mingw32-gcc CXX=i586-mingw32-g++ RANLIB=i586-mingw32-ranlib \
    DLLTOOL=i586-mingw32-dlltool LD=i586-mingw32-ld NM=i586-mingw32-nm \
    ../configure --host=i586-mingw32 --with-mingw --enable-dnd=no
 
 -> CC=i586-mingw32-gcc CXX=i586-mingw32-g++ RANLIB=i586-mingw32-ranlib \
    DLLTOOL=i586-mingw32-dlltool LD=i586-mingw32-ld NM=i586-mingw32-nm \
    ../configure --host=i586-mingw32 --with-mingw --enable-dnd=no
 

-(assuming you're using mingw32)
-
-The important thing to notice here is that we suply configure with the names
-of all the non-default binutils (make sure they're in the PATH!), and that 
-we tell configure to build for the host platform i586-mingw32. 
+(all assuming you're using mingw32)

 Drag'n'drop is disabled because mingw32 lacks (AFAIK) OLE headers.
 
 Configure will conclude that shared libraries are out of the question and
 opt for a static one. I haven't looked into DLL creation yet.
 
 Drag'n'drop is disabled because mingw32 lacks (AFAIK) OLE headers.
 
 Configure will conclude that shared libraries are out of the question and
 opt for a static one. I haven't looked into DLL creation yet.
 

-When configure is finished, examine setup.h in the win32 directory. Search for
-wxUSE_DYNLIB_CLASS, it will be defined twice. Remove the second define (0).
-If your cross-compiler is egcs-based, you might want to add #define __EGCS__
-in setup.h (only used by common/timercmn.cpp).
-

 Type 
 -> make -C src
 and wait, wait, wait. Don't leave the room, because the minute you do there
 Type 
 -> make -C src
 and wait, wait, wait. Don't leave the room, because the minute you do there


@@ -136,9 +170,8 @@ want to rename the cross-compiled one to i586-mingw32-wx-config, or something.
 Cross-compiling TODO:
 ---------------------
 - resource compiling must be done manually for now (should/can we link the 
 Cross-compiling TODO:
 ---------------------
 - resource compiling must be done manually for now (should/can we link the 

-default wx resources into libwx_msw.a?)
+default wx resources into libwx_msw.a?) [ No we can't; the linker won't
+link it in... you have to supply an object file ]

 - dynamic libraries
 - static executables are HUGE -- there must be room for improvement.
 - dynamic libraries
 - static executables are HUGE -- there must be room for improvement.

-- wxUSE_DYNLIB_CLASS double def is probably a bug in configure.in
-- figure out a clean way to determine we're building with configure
-- possibly some problems with parser.y and lexer.c and the like.
+