X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/21de777f02cbf2c9cdbeabf64a6b52c329451023..33785d9f22d92717aedef5249210e03b69bdff5c:/docs/msw/install.txt diff --git a/docs/msw/install.txt b/docs/msw/install.txt index dbcb7c81d6..c49c5e80ae 100644 --- a/docs/msw/install.txt +++ b/docs/msw/install.txt @@ -1,11 +1,10 @@ -Installing wxWindows 2.5.0 +Installing wxWindows 2.5.1 -------------------------- -This is wxWindows 2.5.0 for Microsoft Windows 9x/ME, Windows NT, Windows 2000 +This is wxWindows 2.5.1 for Microsoft Windows 9x/ME, Windows NT, Windows 2000 and Windows XP. This is an unstable development release. Note that unstable in this context doesn't mean that it crashes a lot, just that the library API may -change in backwards incompatible way during the 2.5 branch life time. - +change in backwards incompatible way during the 2.5 branch lifetime. IMPORTANT NOTE: If you experience problems installing, please re-read this instructions and other related files (changes.txt, @@ -19,30 +18,23 @@ Please report bugs using the SourceForge bug tracker: http://sourceforge.net/bugs/?group_id=9863 - Unarchiving =========== A setup program is provided (setup.exe) to automatically copy files to a directory on your hard disk. Do not install into a -path that contains spaces. To avoid confusion with other -wxWindows installations that might be on your machine, the -installation program does not se the WXWIN environment variable; -please set this by hand via the System applet if you wish to -make it permanent. +path that contains spaces. The setup program contains the following: - All common, generic and MSW-specific wxWindows source; -- samples; -- documentation in Windows Help format; +- samples and demos; +- documentation in MS HTML Help format; - makefiles for most Windows compilers, plus CodeWarrior, BC++ and VC++ IDE files; - JPEG library source; - TIFF library source; -- Object Graphics Library; -- Tex2RTF source; -- Dialog Editor binary. +- Object Graphics Library, Tex2RTF, wxSTC, etc. Alternatively, you may unarchive the .zip form by hand: wxMSW-x.y.z.zip where x.y.z is the version number. @@ -50,14 +42,6 @@ wxMSW-x.y.z.zip where x.y.z is the version number. Unarchive the required files plus any optional documentation files into a suitable directory such as c:\wx. -Other add-on packages are available from the wxWindows Web site, such as: - -- mmedia.zip. Audio, CD, video access for Windows and Linux. -- ogl3.zip. Object Graphics Library: build network diagrams, CASE tools etc. -- tex2rtf3.zip. Tex2RTF: create Windows Help, HTML, and Word RTF files from - the same document source. - - General installation notes ========================== @@ -65,7 +49,6 @@ If installing from the CVS server, copy include/wx/msw/setup0.h to include/wx/msw/setup.h and edit the resulting file to choose the features you would like to compile wxWindows with[out]. - Compilation =========== @@ -79,14 +62,13 @@ Where compiled files are stored ------------------------------- After succesful compilation you'll find the libraries in a subdirectory -of lib directory named after the compiler, toolkit name and DLL and Unicode -settings. A couple of examples: +of lib directory named after the compiler and DLL/staitc settings. +A couple of examples: - lib\vc_msw VC++ compiled static libraries - lib\vc_mswdll VC++ DLLs - lib\bcc_mswud Static libraries for Borland C++, - Unicode debug build - lib\wat_mswunivdll Watcom C++ DLLs of wxUniversal port + lib\vc_lib VC++ compiled static libraries + lib\vc_dll VC++ DLLs + lib\bcc_lib Static libraries for Borland C++ + lib\wat_dll Watcom C++ DLLs Names of compiled wxWindows libraries follow this scheme: libraries that don't depend on GUI components begin with "wxbase" followed by version number and @@ -103,12 +85,27 @@ libraries (release versions on left, debug on right side): wxmsw25_html.lib wxmsw25d_html.lib wxmsw25_adv.lib wxmsw25d_adv.lib -These directories also contain wx/setup.h header. +Their Unicode debug counterparts in wxUniversal build would be + + wxbase25ud.lib + wxbase25ud_net.lib + wxbase25ud_xml.lib (notice these libs are same for wxUniv and wxMSW) + wxmswuniv25ud_core.lib + wxmswuniv25ud_html.lib + wxmswuniv25ud_adv.lib + +These directories also contain subdirectory with wx/setup.h header. This +subdirectory is named after port, Unicode, wxUniv and debug settings and +you must add it to include paths when compiling your application. Some +examples: + + lib\vc_lib\msw\wx\setup.h VC++ static, wxMSW + lib\vc_lib\mswud\wx\setup.h VC++ static, wxMSW, Unicode, debug + lib\vc_lib\mswunivd\wx\setup.h VC++ static, wxUniversal, debug Below are compiler specific notes followed by customizing instructions that apply to all compilers (search for "Configuring the build"). - Microsoft Visual C++ compilation -------------------------------- @@ -134,6 +131,9 @@ Using project files (VC++ 6 and later): know you won't need some of the libraries (i.e. html part), you don't have to compile it. It will also produce similar variations on jpeg.lib, png.lib, tiff.lib, zlib.lib, and regex.lib. + If you want to build DLLs, you have to either build them one by one in + proper order (jpeg, png, tiff, zlib, regex, expat, base, core, the rest + in any order) or to use wx_dll.dsw workspace which has correct dependencies. 3. Open a sample project file, choose a configuration such as Win32 Debug using Build | Set Active Configuration..., and compile. The project files don't use precompiled headers, to save disk @@ -152,6 +152,7 @@ Using makefiles: to make the wxWindows core library as release DLL. See "Configuring the build" for instruction how to build debug or static libraries. + 2. Change directory to samples and type 'nmake -f makefile.vc' to make all the samples. You can also make them individually. @@ -173,35 +174,16 @@ project files are now (hopefully) compatible where static libraries are concerned, but please exercise caution nevertheless and if possible, use one method or the other. -Note (3): VC++ 5's optimization code seems to be broken and can -cause both compile and run-time problems: this can be seen when -deleting an object Dialog Editor, in Release mode with optimizations -on. If in doubt, switch off optimisations, although this will result in much -larger executables. It seems possible that the library can be created with -strong optimization, so long as the application is not strongly -optimized. For example, in wxWindows project, set to 'Minimum -Size'. In Dialog Editor project, set to 'Customize: Favor Small -Code' (and no others). This will then work. - -Note (4): some crash problems can be due to inconsistent compiler +Note (3): some crash problems can be due to inconsistent compiler options. If strange/weird/impossible things start to happen please check (dumping IDE project file as makefile and doing text comparison if necessary) that the project settings, especially the list of defined symbols, struct packing, etc. are exactly the same for all items in the project. After this, delete everything (including PCH) and recompile. -Note (5): to create your own IDE files, see the technical note on the -wxWindows web site or CD-ROM, entitled "Compiling wxWindows -applications in the VC++ IDE" (technical note docs/tech/tn0010.htm in the -wxWindows distribution). You can also copy .dsp and .dsw -files from an existing wxWindows sample and adapt them. - - -Visual C++ 1.5 compilation (16-bit) ------------------------------------ - -No longer supported - +Note (4): to create your own IDE files, copy .dsp and .dsw +files from an existing wxWindows sample and adapt them, or +visit http://wiki.wxwindows.org/wiki.pl?MSVC. Borland C++ 5.0/5.5 compilation ------------------------------- @@ -210,11 +192,11 @@ Compiling using the makefiles (updated 24 Sept 02): 1. Change directory to build\msw. Type 'make -f makefile.bcc' to make the wxWindows core library. Ignore the compiler warnings. - This produces a couple of librarie in the lib\bcc_mswdll directory. + This produces a couple of libraries in the lib\bcc_lib directory. 2. Change directory to a sample or demo such as samples\minimal, and type 'make -f makefile.bcc'. This produces a windows exe file - by default - in the bcc_mswdll subdirectory. + in the bcc_mswd subdirectory. Note (1): the wxWindows makefiles assume dword structure alignment. Please make sure that your own project or makefile settings use the @@ -226,39 +208,14 @@ either install odbc32.lib from the BC++ CD-ROM into your BC++ lib directory, or set wxUSE_ODBC to 0 in include\wx\msw\setup.h and recompile wxWindows. 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. -Compiling using the IDE files: [Borland C++ 5.0, not Cbuilder] - -1. Load src\bc32.ide from the file bc32.zip at - http://biolpc22.york.ac.uk/pub/ports/bcc32/wxwin21/ and select Release settings -2. Go to Options|Project... and specify the correct BC++ include and lib path for - your file structure. -3. Press F9 to compile the wxWindows library. -4. Load samples\bc32.ide. -5. Go to Options|Project... and specify the correct BC++ include and lib path for - your file structure. -6. Press F9 to compile the samples (build each node separately if - you prefer, by right clicking and choose Build Node). -7. Run each sample: you may need to run from each sample's directory - since some (notably the wxHTML samples) look for files - relative to the working directory. - -Note (1): the samples project file contains a selection of -samples, and not all samples. The remaining samples can be made -with the makefiles. See also the demos hierarchy which doesn't -have any BC++ project files yet. +Compiling using the IDE files for Borland C++ 5.0: not supported - please +use version 2.4.1 (using the make utility in commandline mode works fine_ -Note (2): to make the png, zlib, jpeg and tiff libraries (needed for -some samples) you need to compile them with bc32.ide. - -Note (3): the debug version of the wxWindows library is about 40 MB, and the -release version is around 5 MB. - -See also the file docs/tech/tn0007.txt for further instructions and details -of how to create your own project files. +Compiling using CBuilder (v1-v6): not supported - please +use version 2.4.1 (using the make utility in commandline mode works fine_ ** REMEMBER ** @@ -272,22 +229,6 @@ the following preprocessor directive: (check the samples -- e.g., \wx2\samples\minimal\minimal.cpp -- for more details) - -Borland C++Builder IDE compilation ----------------------------------- - -1. Build the wxWindows libraries using the Borland make utility as - specified in the section called "Borland C++ 5.0 compilation" - above. (C++ Builder includes a stand-alone C++ compiler. For example, - C++ Builder 4.0 comes with C++ 5.4.) - -2. You can use the process_sample_bcb.bat command which is in - wxwindows\distrib\msw to generate a .mak or .bpr file for most of the - samples [mak for Cbuilder 1-6; v4 and after will convert this to bpr]. - Execute this in the sampledirectory, passing the name of the cpp files - on the command line. For more details, see the instructions in - docs/tech/tn0004.htm or http://biolpc22.york.ac.uk/wx/bc/ide.html. - Borland 16 Bit compilation for Windows 3.1 ------------------------------------------ @@ -299,10 +240,10 @@ Watcom C++ 10.6/11 and OpenWatcom compilation 1. Change directory to build\msw. Type 'wmake -f makefile.wat' to make the wxWindows core library. + 2. Change directory to samples\minimal and type 'wmake -f makefile.wat' to make this sample. Repeat for other samples of interest. - Note (1): if your installation of Watcom doesn't have odbc32.lib file and you need it (i.e. you have wxUSE_ODBC=1), you can use the file from lib\watcom directory. See the notes in that directory. @@ -318,12 +259,12 @@ Note (4): if Watcom can't read the precompiled header when building a sample, try deleting .pch files in build\msw\wat_* and compiling the sample again. - Metrowerks CodeWarrior compilation ---------------------------------- 1. CodeWarrior Pro7 project files in XML format are already - included in wxMSW-2.5.0.zip and the setup version. + included in wxMSW-2.5.1.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 what you want. If you aren't sure, leave it alone and go with the @@ -332,11 +273,13 @@ Metrowerks CodeWarrior compilation - wxUSE_GLOBAL_MEMORY_OPERATORS works, but memory leak reports will be rather confusing due to interactions with the MSL ANSI and runtime libs. + 3. The project file to build the Win32 wxWindows libraries relies on the Batch File Runner plug-in. This plug-in is not installed as part of a normal CW7 installation. However, you can find this plug-in on the CodeWarrior Reference CD, in the Thrill Seekers folder; it's call the "Batch File Post Linker". + 4. If you choose not to install the Batch File Runner plug-in, then you need to do the following by hand: (1) Create the directories lib\cw7msw\include\wx and copy the file @@ -345,31 +288,36 @@ Metrowerks CodeWarrior compilation (2) Create the directories lib\cw7mswd\include\wx and copy the file include\wx\msw\setup.h (or include\wx\msw\setup0.h if you are working from the CVS version) to lib\cw7mswd\include\wx\setup.h + 5. Import src\wxWindowsW7.xml to create the project file wxWindowsW7.mcp. Store this project file in directory src. You may get warnings about not being able to find certain project paths; ignore these warnings, the appropriate paths will be created during the build by the Batch File Runner. + 6. Choose the wxlib Win32 debug or wxlib Win32 Release target and build. You will get some warnings about hidden virtual functions, illegal conversions from const pointers to pointers, etc., all of which you can safely ignore. ***Note: if you get errors that the compiler can't find "wx/setup.h", just stop the build and build again. These errors occur because sometimes the compiler starts doing its thing before the copying of setup.h has completed. + 7. The following libraries will be produced depending on chosen target: - wx_x86.lib ANSI Release (static) - wx_x86_d.lib ANSI Debug (static) + 8. Sorry, I haven't had time yet to create and test unicode or DLL versions. Volunteers for this are welcome (as neither DLLs nor unicode builds are big priorities for me ;). + 9. CodeWarrior Pro7 project files (in XML format) are also provided for some of the samples. In particular, there are project files for the minimal, controls, dialogs, dnd, nd docview samples. You can use these project files as templates for the other samples and for your own projects. - - For example, to make a project file for the "newgrid" sample, + - For example, to make a project file for the "grid" sample, just copy the project file for the "minimal" sample, minimalW7.mcp (made by importing minimalW7.xml into CodeWarrior), into the - sample/newgrid directory, calling it newgridW7.mcp. Open + sample/grid directory, calling it gridW7.mcp. Open newgridW7.mcp and revise the project by deleting the files minimal.rc and minimal.cpp and adding the files griddemo.rc and griddemo.cpp. Build and run.... @@ -511,7 +459,6 @@ Notes: flagged when the program quits. You can use Cygwin gdb to debug MinGW executables. - OLD VERSIONS: - Modify the file wx/src/cygnus.bat (or mingw32.bat or mingegcs.bat) @@ -534,20 +481,27 @@ and can be downloaded from http://www.digitalmars.com/ 1. You need to download and unzip in turn (later packages will overwrite older files) - Digital Mars C/C++ Compiler Version 8.33 - Basic utilities - beta test C++ Compiler Version 8.34 - from http://www.digitalmars.com/download/freecompiler.html [02 may 03, CE] + Digital Mars C/C++ Compiler Version 8.38 or later + Basic utilities + from http://www.digitalmars.com/download/freecompiler.html -2. Change directory to build\msw. Type 'make -f makefile.dm' to +2. Change directory to build\msw and type 'make -f makefile.dmc' to make the wxWindows core library. -3. Change directory to samples\minimal and type 'make -f makefile.dm' - to make this sample. The mdi and image sample also work; others may give - linker erros due to missing libraries -16-bit compilation is no longer supported. +3. Change directory to samples\minimal and type 'make -f makefile.dmc' + to make this sample. Most of the other samples also work. + + +Note that if you don't have the files makefile.dmc you may create them yourself +using bakefile tool according to the instructions in build\bakefiles\README: + + cd build\bakefiles + bakefile_gen -f dmars -b wx.bkl + bakefile_gen -f dmars -b ../../samples/minimal/minimal.bkl +16-bit compilation is no longer supported. + Configuring the build ===================== @@ -578,7 +532,7 @@ Visual C++: > nmake -f makefile.vc BUILD=debug UNICODE=1 Borland C++: - > nmake -f makefile.bcc -DBUILD=debug -DUNICODE=1 + > make -f makefile.bcc -DBUILD=debug -DUNICODE=1 (Note that you have to use -D to set the variable, unlike in other make tools!) @@ -624,7 +578,7 @@ Advanced options ---------------- MONOLITHIC=1 - Starting with version 2.5.0, wxWindows has the ability to be built as + Starting with version 2.5.1, wxWindows has the ability to be built as several smaller libraries instead of single big one as used to be the case in 2.4 and older versions. This is called "multilib build" and is the default behaviour of makefiles. You can still build single library @@ -736,19 +690,24 @@ compiler name. Examples of directory names: build\msw\bcc_mswunivd SHARED=0, WXUNIV=1, BUILD=debug build\msw\vc_mswunivd ditto, with Visual C++ -Libraries and DLLs are copied into subdirectory of lib directory with same -name as the build\msw subdirectory used for object files: +Libraries and DLLs are copied into subdirectory of lib directory with +name derived from compiler and static/DLL setting and setup.h into directory +with name that contains other settings: lib\bcc_msw - lib\bcc_mswdll - lib\bcc_mswunivd - lib\vc_mswunivd - -Each lib\ subdirectory has wx subdirectory with setup.h. This file is copied -there from include\wx\msw\setup.h (and if it doesn't exist, from -include\wx\msw\setup0.h) and this is the copy of setup.h that is used by all -samples and should be used by your apps as well. If you are doing changes to -setup.h, you should do them in this file, _not_ in include\wx\msw\setup.h. + lib\bcc_lib\msw\wx\setup.h + lib\bcc_dll + lib\bcc_dll\msw\wx\setup.h + lib\bcc_lib + lib\bcc_lib\mswunivd\wx\setup.h + lib\vc_lib + lib\vc_lib\mswunivd\wx\setup.h + +Each lib\ subdirectory has wx subdirectory with setup.h as seen above. +This file is copied there from include\wx\msw\setup.h (and if it doesn't exist, +from include\wx\msw\setup0.h) and this is the copy of setup.h that is used by +all samples and should be used by your apps as well. If you are doing changes +to setup.h, you should do them in this file, _not_ in include\wx\msw\setup.h. If you set CFG to something, the value is appended to directory names. E.g. for CFG=MyBuild, you'll have object files in @@ -759,8 +718,8 @@ for CFG=MyBuild, you'll have object files in and libraries in - lib\bcc_mswMyBuild - lib\bcc_mswdllMyBuild + lib\bcc_libMyBuild + lib\bcc_dllMyBuild etc. By now it is clear for CFG is for: builds with different CFG settings don't @@ -769,18 +728,10 @@ have two static debug builds, one with wxUSE_SOCKETS=0 and one with sockets enabled (without CFG, both of them would be put into same directory and there would be conflict between the files). - General Notes ============= - Debugging: under Windows 95, debugging output isn't output in the same way that it is under NT or Windows 3.1. - Please see DebugView (bin/dbgview.exe in the distribution), also - available from http://www.sysinternals.com and on the wxWindows CD-ROM - under Packages. - -- If you are installing wxWindows 2 from CVS, you may find that - include/wx/msw/setup.h is missing. This is deliberate, to avoid - developers' different setup.h configurations getting confused. - Please copy setup0.h to setup.h before compiling. Also, read - the BuildCVS.txt for other hints. + Please see DebugView available from http://www.sysinternals.com. +