- updated instructions for compiling under win32

This commit is contained in:
Bryce Denney 2001-05-30 18:24:48 +00:00
parent a765644750
commit dd3ec034c7
3 changed files with 72 additions and 57 deletions

View File

@ -63,7 +63,7 @@ Before compiling, you'll need to run the configure script, which will configure
source code to run
on your system, and with your chosen options. There are many
options to 'configure', and you probably don't need any of them.
If you run BeOS, specify '--with-beos' to configure.
For example, if you run BeOS, specify '--with-beos' to configure.
To see a complete list:
<PRE>
@ -107,6 +107,11 @@ You may now compile the source.
unix-> make
</PRE>
<p>
There are <a href="win32.html">separate instructions</a> for compiling
in Windows.
<p>
<HR WIDTH="100%">
<H2>
<A NAME="Setting up environment"></A>Setting up environment

View File

@ -8,45 +8,46 @@ Compiling Bochs on a Win32 platform
</H1>
You can compile bochs on your Win32 machine!
<P>
Coding of the GUI module and the original port were done by David Ross. See
<A HREF="http://www.v.nu/core/Bochs">David Ross's Win32 Bochs port</A>
Coding of the GUI module and the original port were done by David Ross.
<P>
<H2>
Compiling Bochs on your Win32 system with MS Visual C++
</H2>
The original port used batch files to build in each directory. I've
extended this, by allowing the configuration script "./configure" to
create all the Makefiles and config files needed to compile with
NMAKE on your Win32 system. Though, in order to use "./configure",
you need access to a system which can run it. Use a Unix
system, or perhaps the GNU-Win32 layer below.
This step is needed only for the configuration step. You then bring the
source tree over to your Win32 system, and NMAKE will make the
entire tree, and produce a BOCHS.EXE file.
<P>
Currently, you can use all the configure options, <B>except</B> the
"--enable-debugger". This will change, as I only need to change the
Makefile for the debugger, so that it leaves the C files for the
lexer/parser.
<P>
Look in "bochs-yymmdd/.conf.win32-vcpp" for the very few commands
to configure for your win32/MS Visual C++ platform.
<P>
Then move the entire distribution over to your Win32 system.
I suggest the following steps, but many other options are available.
<UL>
<LI>tar it
<LI>gzip it
<LI>FTP it over from Unix to Win32
<LI>C:\> MKDIR C:\BOCHS
<LI>use PKWARE's excellent utility to extract it. (C:\> PKZIP25 -extract -directories file.tgz)
<LI>use NMAKE to compile the whole distribution (C:\bochs\bochs-yymmdd> NMAKE)
<LI>copy the ".bochsrc" file to "bochsrc", and edit it
<LI>if you don't already have a disk image file, create one on a Unix system
and transfer it over.
<LI>start the program. (C:\bochs\bochs-yymmdd\BOCHS.EXE)
</UL>
This has only been tested with MS Visual C++ 6.0.
<p>
The normal build process on a unix system is to run configure to build all the
makefiles and config.h, and then run make to compile Bochs. Configure takes a
large number of command line arguments, for example to disable floating point
or to enable sound blaster emulation. Configure works beautifully on unix
systems to help make the code portable, however it cannot run on Windows.
(Maybe, if you have cygwin.) Therefore, you need to either 1) run configure
on a unix box and copy the makefiles and config.h, or 2) download the
makefiles which are distributed in a separate ZIP file.
<p>
If you want to run configure yourself, consider using the shell script
".conf.win32-vcpp" since it is used to make binary releases. Look at it to
make sure the options make sense for you. You can always run configure by hand
too, but be sure to include the option --with-win32-vcpp so that it creates
makefiles for win32. Copy config.h, Makefile, and the Makefiles in all
subdirectories over to the windows box into the same directory as the Bochs
source. <p>
If you download the makefiles in a ZIP, just extract them into the
same directory as the Bochs source. The config.h and top level Makefile
should end up in the same directory as bochs.h.
<p>
Once the makefiles are installed, building Bochs is easy. Start up an MSDOS
window, run the .BAT file that sets up the environment variables
(C:\vc98\bin\vcvars32.bat on my system), and then run NMAKE in the Bochs
source directory. You will get lots of compile warnings, but hopefully no
fatal errors! At the end, you should see Bochs.exe in the source directory.
<p>
</BODY>
</HTML>

View File

@ -1,22 +1,31 @@
Notes for the Win32 Port
~~~~~~~~~~~~~~~~~~~~~~~~
I changed things around so you can use a Unix machine to
create the Makefiles and config files for use with MS Visual C++ 5.0
Please check out "docs-html/win32.html"
-Kevin
------- original text from David Ross -----------------------------------
- Visual C++ 5.0 is required to build this release.
-
- Unfortunately there are no makefiles yet. In each directory where
- a build.bat file exists, you must type "BUILD" to build the libraries.
- The directories are: memory, gui, iodev, and cpu. After you have done
- this, type "BUILD" in the main directory to compile the remaining files
- and link bochs.exe.
-
- --
- David Ross
- dross@pobox.com
Building Bochs for Win32
------------------------
This has only been tested with MS Visual C++ 6.0.
The normal build process on a unix system is to run configure to build all the
makefiles and config.h, and then run make to compile Bochs. Configure takes a
large number of command line arguments, for example to disable floating point
or to enable sound blaster emulation. Configure works beautifully on unix
systems to help make the code portable, however it cannot run on Windows.
(Maybe, if you have cygwin.) Therefore, you need to either 1) run configure
on a unix box and copy the makefiles and config.h, or 2) download the
makefiles which are distributed in a separate ZIP file.
If you want to run configure yourself, consider using the shell script
".conf.win32-vcpp" since it has been tested. Look at it to make sure
the options make sense for you. You can always run configure by hand too,
just be sure to include the option --with-win32-vcpp so that it creates
makefiles for win32. Copy config.h, Makefile, and the Makefiles in all
subdirectories over to your windows box into the same directory as the Bochs
source.
If you download the makefiles in a ZIP, just extract them into the
same directory as the Bochs source. The config.h and top level Makefile
should end up in the same directory as Bochs.h.
Once the makefiles are installed, building Bochs is easy. Start up an MSDOS
window, run the .BAT file that sets up the environment variables
(C:\vc98\bin\vcvars32.bat on my system), and then run NMAKE in the Bochs
source directory. You will get lots of compile warnings, but hopefully no
fatal errors! At the end, you should see Bochs.exe in the source directory.