mirror of https://github.com/bochs-emu/Bochs
556a8fa8f8
and look at the description at the top. Here's an intro. This patch makes significant changes to the configure script. It adds the lines AC_CANONICAL_HOST and AC_CANONICAL_TARGET which detect the OS and processor type. The configure script, knowing the OS and processor type, can then make intelligent decisions about which CFLAGS are needed and what is the default GUI for that platform. One of the goals of this patch is to make it so that on all supported platforms, "configure;make" will compile cleanly. Configure detects the target platform, but it can be overridden by using --target=___. This is important when using one platform to generate Makefiles and header files for another platform. See config.guess script for the exact details of platform naming. The defaults that are currently implemented in the modified configure script include: If platform is windows* or winnt*, use win32 gui. If platform is cygwin*, use win32 gui and compile with "-mno-cygwin -DWIN32". If platform is macosx* or darwin*, use carbon gui and compile with "-fpascal-strings -fno-common -arch ppc -Wno-four-char-constants -Wno-unknown-pragmas -Dmacintosh" If platform is macos, use macos gui. If platform is beos, use beos gui. If platform is amigaos, use amigaos gui. Otherwise, use X windows gui. |
||
---|---|---|
.. | ||
bios | ||
build | ||
cpu | ||
debug | ||
disasm | ||
doc | ||
docs-html | ||
dynamic | ||
font | ||
fpu | ||
gui | ||
instrument | ||
iodev | ||
memory | ||
misc | ||
patches | ||
.bochsrc | ||
.conf.AIX.4.3.1 | ||
.conf.amigaos | ||
.conf.beos-x86-R4 | ||
.conf.beos-x86-preR4 | ||
.conf.linux | ||
.conf.macos | ||
.conf.macosx | ||
.conf.sparc | ||
.conf.win32 | ||
.conf.win32-cygwin | ||
.conf.win32-vcpp | ||
Bochs.proj.hqx | ||
CHANGES | ||
COPYING | ||
Makefile.in | ||
README | ||
TESTFORM.txt | ||
bochs.h | ||
bochs.rsrc.hqx | ||
bxversion.h.in | ||
config.guess | ||
config.h.in | ||
config.sub | ||
configure | ||
configure.in | ||
install-sh | ||
install-x11-fonts.in | ||
load32bitOShack.cc | ||
logio.cc | ||
macintosh.txt | ||
main.cc | ||
osdep.cc | ||
osdep.h | ||
pc_system.cc | ||
pc_system.h | ||
state_file.cc | ||
state_file.h | ||
test-x11-fonts | ||
win32.txt |
README
Bochs x86 Pentium Emulator Upated: Tue Mar 5 10:55:31 2002 Version: 1.4.pre1 WHAT IS BOCHS? Bochs is a highly portable open source IA-32 (x86) PC emulator written in C++, that runs on most popular platforms. It includes emulation of the Intel x86 CPU, common I/O devices, and a custom BIOS. Currently, bochs can be compiled to emulate a 386, 486 or Pentium CPU. Bochs is capable of running most Operating Systems inside the emulation including Linux, Windows 95, DOS, and Windows NT 4. Bochs was written by Kevin Lawton and is currently maintained by the Bochs project at "http://bochs.sourceforge.net". Bochs can be compiled and used in a variety of modes, some which are still in development. The 'typical' use of bochs is to provide complete x86 PC emulation, including the x86 processor, hardware devices, and memory. This allows you to run OS's and software within the emulator on your workstation, much like you have a machine inside of a machine. Bochs will allow you to run Win '95 applications on a Solaris machine with X11, for example. Bochs is distributed under the GNU LGPL. See COPYING for details. GETTING CURRENT SOURCE CODE Source code for Bochs is available from the Bochs home page at http://bochs.sourceforge.net. You can download the most recent release, use CVS to get the latest sources, or grab a CVS snapshot which is updated nightly. The releases contain the most stable code, but if you want the very newest features try the CVS version instead. WHERE ARE THE DOCS? The Bochs documentation has been overhauled, and it is now distributed in a separate package called bochsdoc-VERSION.tar.gz. A copy is also online at http://bochs.sf.net/doc/docbook/alldocs.html For now, the old documentation can still be found at http://bochs.sf.net/docs-html WHERE CAN I GET MORE INFORMATION? HOW DO I REPORT PROBLEMS? Both the documentation and the Bochs website have instructions on how to join the bochs-developers mailing list, which is the primary forum for discussion of Bochs. The main page of the website also has links to bug reports and feature requests. You can browse and add to the content in these areas even if you do not have a (free) SourceForge account. We need your feedback so that we know what parts of Bochs to improve. There is a patches section on the web site too, if you have made some changes to Bochs that you want to share. HOW CAN I HELP? If you would like contribute to the Bochs project, a good first step is to join the bochs-developers mailing list, and read the archive of recent messages to see what's going on. If you are a technical person (can follow hardware specs, can write C/C++) take a look at the list of open bug reports and feature requests to see if you are interested in working on any of the problems that are mentioned in them. If you check out the CVS sources, make some changes, and create a patch, one of the developers will be very happy to apply it for you. Developers who frequently submit patches, or who embark on major changes in the source can get write access to CVS. Be sure to communicate with the bochs-developers list to avoid several people working on the same thing without realizing it. If you are a Bochs user, not a hardware/C++ guru, there are still many ways you could help out. For example: - improving win32 binary releases - building up a set of useful tools to include in those releases - writing/cleaning up documentation - testing out Bochs on every imaginable operating system and reporting how it goes.