Installing wxWindows 2.1
------------------------
-[Notes from Robert Roebling for snapshot 8]
-
-This is a not-so-well tested snapshot release of wxWindows 2.1 for
-Microsoft Windows 95, 98 and NT. This is not a production release,
+This is a beta release of wxWindows 2.1 for Microsoft
+Windows 95, 98 and NT. This is not a production release,
although a huge number of bugs found in wxWindows 2.0 have been
fixed.
-There have not been major changes in the way to build the library,
-although the creation of the various makefiles has been automatized.
-I myself use the GNU MingGW32 compiler from
-
- http://www.cygnus.com
-
-using the GNU make program from
-
- http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32
-
-and I have not tested any other compiler, but other developers use
-the makefiles for Borland C++, MS-Visual C++ 5.0 and 6.0 and probably
-Metrowerks C++.
-
-Expect problems.
-
-Installing wxWindows 2.0
-------------------------
-
IMPORTANT NOTE: If you experience problems installing, please
-re-read this instructions and other related files (todo.txt,
-bugs.txt etc.) carefully before mailing wxwin-users or
+re-read this instructions and other related files (release.txt,
+todo.txt, bugs.txt etc.) carefully before mailing wxwin-users or
the author. Preferably, try to fix the problem first and
-then send a patch to the author.
+then send a patch to the author. Please report bugs using the
+bug report form on the wxWindows web site.
Unarchiving
-----------
-If there is a setup program, run the setup program that comes with the Windows version.
-Do not install into a path that contains spaces. The installation program should set the
-WXWIN environment variable, which will be activated when your machine is rebooted.
-
-If there is no setup program, it will come as a series of .zip
-files:
-
-wx200gen.zip Generic source code and samples (required)
-wx200msw.zip Windows-specific source code and samples (required)
-wx200doc.zip Documentation source code (not required)
-wx200hlp.zip WinHelp documentation
-wx200pdf.zip Acrobat PDF documentation
-wx200htm.zip HTML documentation
-wx200vc.zip MS VC++ 5.0 project files
-wx200cw.zip Metrowerks CodeWarrior project files
-wx200bc.zip BC++ 5 project files
+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.
+The installation program should set the WXWIN environment variable, which
+will be activated when your machine is rebooted. The setup
+program contains the following:
+
+- All common, generic and MSW-specific wxWindows source;
+- samples;
+- documentation in Windows Help format;
+- makefiles for most Windows compilers, plus BC++ and
+ VC++ IDE files;
+- JPEG library source;
+- Object Graphics Library;
+- wxGLCanvas library;
+- wxTreeLayout library;
+- Tex2RTF source;
+- Dialog Editor binary.
+
+Alternatively, you may unarchive the set of .zip files by hand,
+where x is the minor version number and y is the release number:
+
+wx2_x_y_gen.zip Generic source code and samples (required)
+wx2_x_y_msw.zip Windows-specific source code and samples (required)
+wx2_x_y_doc.zip Documentation source code (not required)
+wx2_x_y_hlp.zip WinHelp documentation
+wx2_x_y_pdf.zip Acrobat PDF documentation
+wx2_x_y_htm.zip HTML documentation
+wx2_x_y_vc.zip MS VC++ 5.0 project files
+wx2_x_y_cw.zip Metrowerks CodeWarrior project files
+wx2_x_y_bc.zip BC++ 5 project files
+jpeg.zip Use this to allow wxImage to read and write JPEG files
Unarchive the required files plus any optional documentation
files into a suitable directory such as c:\wx.
Using project files:
-1. Unarchive wx200vc.zip, the VC++ 5 project makefiles.
+1. Unarchive wx2_x_y_vc.zip, the VC++ 5/6 project makefiles.
2. Open src/wxvc.dsp, set Debug or Release configuration, and
compile. This will produce src/Debug/wxvc.lib or
src/Release/wxvc.lib. The project file src/wxvc_dll.dsp
will make a DLL version of wxWindow, which will go in
src/DebugDLL/wxvc.[lib,dll] and src/ReleaseDLL/wxvc.[lib,dll].
-3. Open a sample project file, choose a configuration, and compile.
+3. If you want to use JPEG in your application (such as the image
+ sample), open src/jpeg/jpeg.dsp (VC++ 5/6 only) and compile in
+ Debug and Release configurations. If you have VC++ 4,
+ use makefile.vc, but you may only have one set of object
+ files at a time in use (debug or release versions).
+4. Open a sample project file, choose a configuration using
+ Build | Set Active Configuration..., and compile.
The project files don't use precompiled headers, to save
space, but you can switch PCH compiling on for greater speed.
to make the wxWindows core library without debug information
(wx\lib\wx.lib).
-
-3. Change directory to wx\samples and type 'nmake -f makefile.vc'
+3. If you wish to use JPEG in your applications, do the same
+ procedure in src\jpeg but add the 'all' target to the
+ command line.
+4. Change directory to wx\samples and type 'nmake -f makefile.vc'
to make all the samples. You can also make them individually.
Notes:
suitable precompiled header file for compiling applications.
The resulting libraries are called:
- wx\lib\wx200_d.lib(dll) (debug version)
+ wx\lib\wx200.lib(dll) (debug version)
wx\lib\wx200.lib(dll) (release version, using FINAL=1)
2. Invoke a sample makefile with 'nmake -f makefile.vc WXUSINGDLL=1'
the other.
Note (3): VC++ 5's optimization code seems to be broken and can
-cause 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
+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.
+Similarly, in VC++ 4, optimization can cause internal compiler
+errors, so edit src\makevc.env and change /O1 to /Od before
+trying build a release version of the library.
+
Note (4): 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
symbols, struct packing, etc. are exactly the same for all items in
the project. After this, delete everything (including PCH) and recompile.
-Visual C++ 1.5 compilation
---------------------------
+Visual C++ 1.5 compilation (16-bit)
+-----------------------------------
1. Make sure your WXWIN variable is set, and uses the FAT (short
name) form.
'make -f makefile.b32 FINAL=1'
for the library and samples.
-Note: the wxWindows library and (some) samples compile in 16-bit mode
+Note (1): the wxWindows library and (some) samples compile in 16-bit mode
using makefile.bcc, but at present the wxWindows resource system is switched
off in this mode. See issues.txt for details.
+Note (2): unfortunately most samples won't link in 16-bit mode,
+because the automatic data segment exceeds 64K. The minimal
+sample links and runs, however.
+
+Note (3): the wxWindows makefiles assume byte structure alignment. Please
+make sure that your own project or makefile settings use the
+same alignment, or you could experience mysterious crashes. To
+change the alignment, add a suitable option to the $(CFG) target code
+in src/msw/makefile.b32.
+
+Note (4): if you get undefined _SQL... symbols at link time,
+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.
+
Compiling using the IDE files:
-1. Load src\bc32.ide (or src\bc32d.ide for a debugging version).
+1. Load src\bc32.ide (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.
+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 that to make the png, xpm and zlib libraries (needed for
-some samples) you need to compile with bc32.ide. bc32d.ide only
-makes the wxWindows library (lib\wx32d.lib).
+Note that to make the png, xpm, zlib and jpeg libraries (needed for
+some samples) you need to compile them with bc32.ide.
The debug version of the wxWindows library is about 37 MB, and the
release version is around 3 MB.
Tested with C++Builder 1.0 and 3.0. Only makefiles are currently
supplied.
-Watcom C++ 10.6 compilation
+Watcom C++ 10.6/11 compilation
---------------------------
1. Make sure your WXWIN variable is set, and uses the DOS short
2. Change directory to wx\src\msw. Type 'wmake -f makefile.wat' to
make the wxWindows core library.
3. Change directory to wx\samples\minimal and type 'wmake -f makefile.wat'
- to make this sample.
+ to make this sample. Repeat for other samples of interest.
+
+Note (1): setup.h overrides wxUSE_LIBJPEG and sets it to 0, since
+imagjpeg.cpp doesn't compile.
+Note (2): makewat.env uses the odbc32.lib supplied in wxWindows' lib\watcom
+directory. See the notes in that directory.
+Note (3): makefile compilation seems broken (28/12/99) with a
+GPF in the linker. Too many object files? Could try switching
+some options off in setup.h.
Metrowerks CodeWarrior compilation
----------------------------------
-1. Downloaded and unzip wx200cw.zip.
+1. Downloaded and unzip wx2_x_y_cw.zip.
2. Load the make_cw.mcp project in wx\src, and compile.
3. Load the make_cw.mcp project in wx\samples\minimal, and compile.
Further project files for samples will be available in due
course.
-NOTES:
-
-You need CodeWarrior Pro 4 plus the patches to 4.1 from the
+Note (1): you need CodeWarrior Pro 4 plus the patches to 4.1 from the
Metrowerks Web site.
+Note (2): unfortunately these files are not yet up-to-date for the
+current release.
+
Symantec C++ compilation
------------------------
Cygwin b19/b20/Mingw32 compilation
----------------------------------
-wxWindows 2.0 supports Cygwin (formerly GnuWin32) b19, b20, Mingw32, and Mingw32/EGCS.
+wxWindows 2 supports Cygwin (formerly GnuWin32) b19, b20, Mingw32, and Mingw32/EGCS.
Thanks are due to Keith Garry Boyce (garp@opustel.com) and Cygnus for making
it all possible.
If you have already have downloaded bison, flex, make, rm, mv
from elsewhere, you won't need this.
- IMPORTANT: also see mingw32.txt in this directory (docs/msw)
- about a fix that has to be applied to a Mingw32 header file.
+ If using Mingw32 2.8.1, see also see mingw32.txt in this directory
+ (docs/msw) about a fix that has to be applied to a Mingw32 header file.
+
+ If using Mingw32 2.95 with wxWindows 2.1 or above, and wish to use OLE, you
+ should hand-patch in Mingw32-gcc295.patches (located in the top-level of the
+ wxWindows 2 installation).
- Modify the file wx/src/cygnus.bat (or mingw32.bat or mingegcs.bat)
to set up appropriate variables, if necessary mounting drives.
- For Cygwin, make sure there's a \tmp directory on your
Windows drive or bison will crash.
-- Edit wx/src/makeg95.env and search for MINGW32. Take note of
- the comments for adjusting settings to suit Cygwin or
- Mingw32. Basically, this is just a case of adding the __MINGW32__ symbol
- to OPTIONS for Mingw32, or removing it for Cygnus Cygwin.
- For Mingw32/EGCS, add both __MINGW32__ and __EGCS__.
- You may need to remove -loldnames from WINLIBS for Mingw32, or add it for
- Cygwin.
+- Edit wx/src/makeg95.env and set the MINGW32 variable at the top of
+ the file to either 1 (you have Mingw32) or 0 (you have Cygwin32).
+ If using MINGW32, also set the MINGW32VERSION variable
+ appropriately.
-- Mingw32 may not support winsock.h, so comment out
- socket-related files in src/msw/makefile.g95.
+- Mingw32 may not support winsock.h, so if you have a problem
+ here, comment out socket-related files in src/msw/makefile.g95.
- Set your WXWIN variable to where wxWindows is installed.
*** IMPORTANT: For Cygwin/Mingw32, use forward slashes in the path, not
Notes:
+- See also the Cygwin/Mingw32 on the web site or CD-ROM for
+ further information about using wxWindows with these compilers.
+
- libwx.a is 48 MB or more - but much less if compiled with no
debug info (-g0) and level 4 optimization (-O4).
isn't available with Cygwin. However, you can use it with external
decompression utilities.
-- Doesn't compile src/msw/ole files, so no drag and drop.
-
-- There's a bug in the Mingw32 headers for some distributions.
+- There's a bug in Mingw32 headers for some early distributions.
in include/windows32/defines.h, where it says:
(a missing bracket).
+- If there's a problem with the copy command in
+ src/msw/makefile.g95, you may need to change the relevant
+ section to the following:
+
+ COPY = command /c copy
+ $(COMMDIR)/y_tab.c: $(COMMDIR)/dosyacc.c
+ $(COPY) ..\\common\\dosyacc.c ..\\common\\y_tab.c
+
+ $(COMMDIR)/lex_yy.c: $(COMMDIR)/doslex.c
+ $(COPY) ..\\common\\doslex.c ..\\common\\lex_yy.c
+
References:
- The GNU-WIN32 site is at
http://www.cygnus.com/gnu-win32/
- Mingw32 is available at:
- http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/index.html
+ ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/gcc-2.95/
- See also http://web.ukonline.co.uk/julian.smart/wxwin/gnuwin32.htm
TWIN32 and gcc on Linux
projects / wxWidgets.git / blobdiff