X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/e28b9b9cb82306050a5f0e2205466631efee01ef..066f3611df971be93b2ec46b82c2f05f3ff9a422:/docs/msw/install.txt diff --git a/docs/msw/install.txt b/docs/msw/install.txt index 11614b5bc0..58c11b8903 100644 --- a/docs/msw/install.txt +++ b/docs/msw/install.txt @@ -1,7 +1,7 @@ -Installing wxWidgets 2.8.0 +Installing wxWidgets for Windows ----------------------------------------------------------- -This is wxWidgets 2.8.0 for Microsoft Windows 9x/ME, Windows NT, +This is wxWidgets for Microsoft Windows 9x/ME, Windows NT, Windows 2000, Windows XP and Windows CE. These installation notes can be found in docs/msw/install.txt @@ -303,12 +303,29 @@ recompile wxWidgets. The same applies if compiling using the IDE. Note (3): If you wish debug messages to be sent to the console in debug mode, edit makefile.bcc and change /aa to /Tpe in link commands. -Cmpilation succeeds with CBuilderX personal edition and CBuilder6, but +Using the Debugger and IDE in BDS or Turbo Explorer +--------------------------------------------------- + + +Doubleclick / open samples\minimal\borland.bdsproj. The current version +is to be used with a dynamic build of wxWidgets-made by running +make -f Makefile.bcc -DBUILD=debug -DSHARED=1 +in wxWidgets\build\msw. You also need the wxWidgets\lib\bcc_dll +directory in your PATH. The debugger tracks your source and aslo +travces into the wxWidgets sources. + +To use this to debug other samples, copy the borland_ide.cpp +and borland.bdsproj files, then replace all occurences of +"minimal" with the name of the new project files + +Compilation succeeds with CBuilderX personal edition and CBuilder6, but you may have to copy make.exe from the 5.5 download to the new bin directory. + Compiling using the IDE files for Borland C++ 5.0 and using CBuilder IDE (v1-v6): not supported + ** REMEMBER ** In all of your wxWidgets applications, your source code should include @@ -368,7 +385,7 @@ Metrowerks CodeWarrior compilation ** The authoritative list of files is in build/bakefiles/files.bkl 1. CodeWarrior Pro 7 project files in XML format are already - included in wxMSW-2.8.0.zip and the setup version. + included in wxMSW-2.8.x.zip and the setup version. 2. Review the file include\wx\msw\setup.h (or include\wx\msw\setup0.h if you are working from the CVS version) to make sure the settings reflect @@ -685,9 +702,9 @@ SHARED=1 Build shared libraries (DLLs). By default, DLLs are not built (SHARED=0). -UNICODE=1 - To build Unicode versions of the libraries, add UNICODE=1 to make invocation - (default is UNICODE=0). If you want to be able to use Unicode version on +UNICODE=0 + To build ANSI versions of the libraries, add UNICODE=0 to make invocation + (default is UNICODE=1). If you want to be able to use Unicode version on Windows9x, you will need to set MSLU=1 as well. This option affect name of the library ('u' is appended) and the directory @@ -761,6 +778,10 @@ DEBUG_INFO=1 Same as DEBUG_FLAG in behaviour, this option affects whether debugging information is included in the executable or not. +TARGET_CPU=AMD64|IA64 + (VC++ only.) Set this variable to build for x86_64 systems. If unset, x86 + build is performed. + VENDOR= Set this to a short string identifying your company if you are planning to distribute wxWidgets DLLs with your application. Default value is 'custom'. @@ -775,6 +796,14 @@ CFG= different setup.h settings coexisting in same tree. See "Object and library directories" below for more information. +COMPILER_PREFIX= + If you build with multiple versions of the same compiler, you can put + their outputs into directories like "vc6_lib", "vc8_lib" etc. instead of + "vc_lib" by setting this variable to e.g. "vc6". This is merely a + convenience variable, you can achieve the same effect (but different dir + names) with the CFG option. + + Compiler specific options ----------------------------------------------------------------