![]() ![]() + diff -git a/bochs/COPYING b/bochs/COPYING +(visit for more information) + +HOW TO BUILD + + Just run make like, + $ make + + To clean up, + $ make clean + +OUTPUT + + The two binaries rombios16.bin and +copied from the directories accordingly, and renamed to bios.bin and +vgabios-cirrus.bin. + + commit 33636cbdd93da79c903b91b50ae087bb814b9332 + Author: vruppert + Date: Mon Jan 31 17:28:09 2011 +0000 + + - added HDTV resolutions (patch by Tristan Schmelcher) + +TOOLS REQUIRED TO BUILD + + The build requires dev86 rpm or bin86 & bcc debs version >= 0.16.14. + ++ vgabios-cirrus.bin: git:///pub/scm/virt/vgabios/vgabios.git + + The file vgabios-cirrus.bin is, which +is built by the tree, and we used the following commit. We used the following commit in the bochs git tree so that +it can match with the qemu tree in platform/external/qemu: + + commit 04387139e3b5ac97b5633cd40b3d87cdf45efd6c + Author: sshwarts + Date: Mon Feb 9 19:46:34 2009 +0000 + + Fixed compilation error + x86-64 correctness fix + + Since our purpose is to build only rombios16.bin, we populated part +of the bochs tree in the git tree above. + + +SOURCE CODE + ++ bios.bin: git:///pub/scm/virt/bochs/bochs.git + + The file bios.bin is actually rombios16.bin, which is built from +bochs/bios. +++ -0,0 +1,52 project has the source code to build two binaries: bios.bin and +vgabios-cirrus.bin, which are required for x86 emulation in the +Android emulator: platform/external/qemu. configure + +bios.bin: bochs/bios/Makefile + $(MAKE) -C bochs/bios + $(CP) bochs/bios/rombios16.bin + +vgabios-cirrus.bin: + $(MAKE) -C vgabios + $(CP) vgabios/ + +clean: + rm -rf bochs/Makefile bochs/build bochs/config.h bochs/config.log \ + bochs/config.status bochs/instrument bochs/ltdlconf.h + $(MAKE) -C bochs/bios bios-clean + $(MAKE) -C bochs/bios dist-clean + $(MAKE) -C vgabios bios-clean + $(MAKE) -C vgabios dist-clean + rm -rf bios.bin vgabios-cirrus.bin + + + + diff -git a/README b/README +# + +CC := gcc +BCC := bcc +AS86 = as86 +MAKE := make +CP := cp + +all: bios.bin vgabios-cirrus.bin + +bochs/bios/Makefile: + cd bochs &. +# + +# this is a set of definitions that allow the usage of Makefile.android +# even if we're not using the Android build system. +# See the License for the specific language governing permissions and +# limitations under the License. +# You may obtain a copy of the License at +# +# +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +++ -0,0 +1,50 Copyright (C) 2011 The Android Open Source Project +# +# Licensed under the Apache License, Version 2.0 (the "License") +# you may not use this file except in compliance with the License. Merge "x86: source code to build two binaries: bios.bin and vgabios-cirrus.bin, which are required for x86 emulation in the Android x86 emulator." diff -git a/Makefile b/Makefile ![]() Infact, you will get bored of this in less than a day.įinally, its not the os from windows phones. And android and that OS will both run together until you exit the app. Your pc wont turn in to that os, but both OSes will run simultaneously. Its like using virtualisation programs like virtualbox on pc. As I already said, you wont be able to make use of any major function. Will running virtual machine on Android completely turn my Android But other than that, there's no purpose, atleast for now. The only thing its good for is that you can say "Hey look! I got windows in my phone". I have personally tried Ubuntu 12.04 and a stripped off version of windows xp. So until BOCHS supports multi-threading and some other things, its almost useless to try that. Even if the android hardware is good enough, BOCHS hasnt developed to that level yet. Forget games, even mugen doesn't run properly. You can install older OSes like windows xp (on phones like s5-s6 or similar) or windows 98, but again, no real softwares could be run. Infact, even you you managed to install just the os, the hardware wont be enough t or run any app and interface will be far too pain. And till now, individual processor cores aren't that strong for any android till today to run any modern OS as intended. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |