android-x86編譯

阿新 • • 發佈：2019-01-17

編譯環境Ubuntu 11.04 - 64位作業系統

1：首先安裝jdk

到Ubuntu自帶的軟體包，安裝即可，方便簡單

2：以此執行如下命令

sudo apt-get install bison  
sudo apt-get install libc6-dev-i386  
sudo apt-get install zlib1g-dev  
sudo apt-get install g++-multilib  
sudo apt-get install lib32z1-dev  
sudo apt-get install flex  
sudo apt-get install lib32ncurses5-dev  
sudo apt-get install gperf  
sudo apt-get install libx11-dev

執行的時候注意觀察是否執行成功

失敗的時候需要重新安裝

3：在x86的原始碼包的根目錄

依次執行如下命令

source build/envsetup.sh  
lunch  
make iso_img -j4

其中會顯示如下：

[email protected]:~/android-froyo$ source build/envsetup.sh including device/asus/eeepc/vendorsetup.sh including device/asus/laptop/vendorsetup.sh including device/dell/sparta/vendorsetup.sh including device/viewsonic/viewpad10/vendorsetup.sh including device/vm/vm/vendorsetup.sh

[email protected]:~/android-froyo$ lunch

You're building on Linux

Lunch menu... pick a combo: 1. generic-eng 2. generic_x86-eng 3. simulator 4. eeepc-eng 5. asus_laptop-eng 6. sparta-eng 7. viewpad10-eng 8. vm-eng

然後輸入2 回車，

然後make 即可。因為我試了N多次，才成功，所以整個過程耗得時間較長

陸陸續續的搗鼓了倆周。

望大家一定要有耐心

make完成以後會在 out/target/product/genetic_x86 目錄下生成一個iso映象檔案，用該檔案在虛擬機器中啟動即可

以下是安裝成功後的顯示結果

【編譯中遇到的問題見點選開啟連結】

看著真激動啊。。昨晚2點make成功。紀念一下

genisoimage 1.1.11 (Linux)
Scanning out/target/product/generic_x86/boot
Scanning out/target/product/generic_x86/boot/isolinux
Writing:   Initial Padblock                        Start Block 0
Done with: Initial Padblock                        Block(s)    16
Writing:   Primary Volume Descriptor               Start Block 16
Done with: Primary Volume Descriptor               Block(s)    1
Writing:   Eltorito Volume Descriptor              Start Block 17
Size of boot image is 4 sectors -> No emulation
Done with: Eltorito Volume Descriptor              Block(s)    1
Writing:   Joliet Volume Descriptor                Start Block 18
Done with: Joliet Volume Descriptor                Block(s)    1
Writing:   End Volume Descriptor                   Start Block 19
Done with: End Volume Descriptor                   Block(s)    1
Writing:   Version block                           Start Block 20
Done with: Version block                           Block(s)    1
Writing:   Path table                              Start Block 21
Done with: Path table                              Block(s)    4
Writing:   Joliet path table                       Start Block 25
Done with: Joliet path table                       Block(s)    4
Writing:   Directory tree                          Start Block 29
Done with: Directory tree                          Block(s)    2
Writing:   Joliet directory tree                   Start Block 31
Done with: Joliet directory tree                   Block(s)    2
Writing:   Directory tree cleanup                  Start Block 33
Done with: Directory tree cleanup                  Block(s)    0
Writing:   Extension record                        Start Block 33
Done with: Extension record                        Block(s)    1
Writing:   The File(s)                             Start Block 34
  1.63% done, estimate finish Sun Aug 21 01:21:08 2011
  3.26% done, estimate finish Sun Aug 21 01:21:08 2011
  4.90% done, estimate finish Sun Aug 21 01:20:47 2011
  6.53% done, estimate finish Sun Aug 21 01:20:37 2011
  8.16% done, estimate finish Sun Aug 21 01:20:31 2011
  9.79% done, estimate finish Sun Aug 21 01:20:47 2011
 11.42% done, estimate finish Sun Aug 21 01:20:50 2011
 13.05% done, estimate finish Sun Aug 21 01:20:45 2011
 14.69% done, estimate finish Sun Aug 21 01:20:41 2011
 16.32% done, estimate finish Sun Aug 21 01:20:43 2011
 17.95% done, estimate finish Sun Aug 21 01:20:40 2011
 19.58% done, estimate finish Sun Aug 21 01:20:42 2011
 21.21% done, estimate finish Sun Aug 21 01:20:58 2011
 22.84% done, estimate finish Sun Aug 21 01:20:55 2011
 24.48% done, estimate finish Sun Aug 21 01:20:51 2011
 26.11% done, estimate finish Sun Aug 21 01:20:52 2011
 27.74% done, estimate finish Sun Aug 21 01:20:50 2011
 29.37% done, estimate finish Sun Aug 21 01:20:58 2011
 31.00% done, estimate finish Sun Aug 21 01:20:55 2011
 32.63% done, estimate finish Sun Aug 21 01:20:52 2011
 34.27% done, estimate finish Sun Aug 21 01:20:50 2011
 35.90% done, estimate finish Sun Aug 21 01:20:51 2011
 37.53% done, estimate finish Sun Aug 21 01:20:49 2011
 39.16% done, estimate finish Sun Aug 21 01:20:50 2011
 40.79% done, estimate finish Sun Aug 21 01:20:48 2011
 42.42% done, estimate finish Sun Aug 21 01:20:49 2011
 44.06% done, estimate finish Sun Aug 21 01:20:47 2011
 45.69% done, estimate finish Sun Aug 21 01:20:50 2011
 47.32% done, estimate finish Sun Aug 21 01:20:49 2011
 48.95% done, estimate finish Sun Aug 21 01:20:49 2011
 50.58% done, estimate finish Sun Aug 21 01:20:52 2011
 52.21% done, estimate finish Sun Aug 21 01:20:51 2011
 53.85% done, estimate finish Sun Aug 21 01:20:53 2011
 55.48% done, estimate finish Sun Aug 21 01:20:52 2011
 57.11% done, estimate finish Sun Aug 21 01:20:52 2011
 58.74% done, estimate finish Sun Aug 21 01:20:52 2011
 60.37% done, estimate finish Sun Aug 21 01:20:53 2011
 62.00% done, estimate finish Sun Aug 21 01:20:52 2011
 63.64% done, estimate finish Sun Aug 21 01:20:52 2011
 65.27% done, estimate finish Sun Aug 21 01:20:52 2011
 66.90% done, estimate finish Sun Aug 21 01:20:53 2011
 68.53% done, estimate finish Sun Aug 21 01:20:52 2011
 70.16% done, estimate finish Sun Aug 21 01:20:51 2011
 71.79% done, estimate finish Sun Aug 21 01:20:51 2011
 73.43% done, estimate finish Sun Aug 21 01:20:51 2011
 75.06% done, estimate finish Sun Aug 21 01:20:53 2011
 76.69% done, estimate finish Sun Aug 21 01:20:53 2011
 78.32% done, estimate finish Sun Aug 21 01:20:54 2011
 79.95% done, estimate finish Sun Aug 21 01:20:53 2011
 81.58% done, estimate finish Sun Aug 21 01:20:53 2011
 83.22% done, estimate finish Sun Aug 21 01:20:53 2011
 84.85% done, estimate finish Sun Aug 21 01:20:54 2011
 86.48% done, estimate finish Sun Aug 21 01:20:54 2011
 88.11% done, estimate finish Sun Aug 21 01:20:54 2011
 89.74% done, estimate finish Sun Aug 21 01:20:53 2011
 91.37% done, estimate finish Sun Aug 21 01:20:54 2011
 93.01% done, estimate finish Sun Aug 21 01:20:53 2011
 94.64% done, estimate finish Sun Aug 21 01:20:53 2011
 96.27% done, estimate finish Sun Aug 21 01:20:52 2011
 97.90% done, estimate finish Sun Aug 21 01:20:52 2011
 99.53% done, estimate finish Sun Aug 21 01:20:53 2011
Total translation table size: 4495
Total rockridge attributes bytes: 1372
Total directory bytes: 2048
Path table size(bytes): 26
Done with: The File(s)                             Block(s)    306258
Writing:   Ending Padblock                         Start Block 306292
Done with: Ending Padblock                         Block(s)    150
Max brk space used 21000
306442 extents written (598 MB)

android-x86編譯

編譯環境Ubuntu 11.04 - 64位作業系統 1：首先安裝jdk 到Ubuntu自帶的軟體包，安裝即可，方便簡單 2：以此執行如下命令 sudo apt-get install bison sudo apt-get install libc6-dev-i386

為Android-x86編譯tcpdump工具

在谷歌和必應上搜索的Android-x86專用的tcpdump工具多半不能使用，它們基本上都是在ARM架構的安卓手機上使用的，而且版本都較為老舊。由於Android-x86的Linux核心是通用的32位Linux，那麼能否在常用的32位Linux發行版上直接使用32位的gc

android -x86 編譯中遇到的問題

錯誤1： build/core/base_rules.mk:69: unusual tags systembuilder on badblocks at external/e2fsprogs/misc target Dex: framework target SharedL

android原始碼編譯錯誤make ***[out/host/linux-x86/obj/EXECUTABL

系統是Ubuntu1264位，2G記憶體，編譯的時候出現下面這個錯誤： make:***[out/host/linux-x86/obj/EXECUTABLES/llvm-rs-cc_intermediates/llvm-rs-cc]Error1make:***Waitingforunfinishe

code::Blocks 中配置android x86的編譯環境

之前是android arm 的編譯環境，現需改為android x86的環境 1. Project-->build options, 選擇android平臺，selected compiler 選擇 GNU GCC Compiler，之前arm環境選的是 GNU G

指定Android Studio編譯工程時的源文件編碼

javac Coding 設置 odin images utf8編碼 androi mage nco 統一設置為UTF8編碼在工程的根目錄下的build.gradle文件中，添加定義。tasks. withType(JavaCompile) { options.enc

android反編譯odex文件

lis 目錄 trac 依賴 andro xheditor span sys 放置關於android的反編譯工具，相信大家並不陌生如APK-TOOL，dex2jar APK-TOOL 用於反編譯出布局文件下載地址http://code.google.co

cocos2d-x 移植到android中編譯的一些問題：fatal error: Box2D/Box2D.h: No such file or directory"

cocos2 app nal get dsc err 2dx ros blue 1、fatal error: Box2D/Box2D.h: No such file or directory" 須要加入box2d庫的支持，改動android.mk

android ndk 編譯的時候指令集的選取

文章 span tag androi ndk 有時 oca class word android ndk在編譯的時候默認生成的是thumb指令（拇指）不是arm（手臂）指令，但是有時候在看反匯編的時候，不太熟悉thumb指令或者說thumb指令看起來更費勁，需要生成arm指

Android 關於編譯ijkplayer下的so經驗分享

本地 pat 經驗變量一次公司 https 調研 vmw 前言：公司最近需要做直播方面的技術調研，所以需要去研究播放器相關的技術；剛好本人github上收藏了ijkplayer，之前一直沒有研究過，現在剛好clone下來研究研究。我先在Windows安裝c

【Android】Ubuntu 16.04搭建Android開發編譯環境

jdk8 per 參考 prot google官網 markdown ins 由於 log 一. 通用Android環境和工具配置 1. 系統更新升級 sudo apt-get update sudo apt-get upgrade 2. 配置ntlmaps代理上網環境

【Cocos2d-x 3.0】遊戲開發之android交叉編譯

plain edit 100% b2c 令行 sdk 自己的路 smi bin 作者：Senlern 轉載請註明，原文鏈接：http://blog.csdn.net/zhang429350061/article/details/37959489 在上

Android系統編譯出錯

android 編譯出錯在Android7.1編譯過程中出現如下錯誤：Starting build with ninjaninja: Entering directory `.‘ [ 0% 8/30301] Ensure Jack server is installed and startedJack

android studio 編譯C文件出錯

android c1、還要在gradle.properties裏面加上這麽一句話：android.useDeprecatedNdk=true 2、打開app Module的build.gradle文件，在defaultConfig節點裏添加以下代碼註意這裏的moduleName，是我們在之前自己編寫的類裏面

如何為Android平臺編譯 opencv3 和 opencv_contrib (Linux)

gre inter jni fuzzy dnn letter ott esc lis p { margin-bottom: 0.1in; direction: ltr; color: rgb(0, 0, 10); line-height: 120%; text-align:

OSG for android的編譯總結

display article 原因 mat cygwin 動態鏈接 cep evel arr 最近對OSG進行了android下的編譯。簡單總結一下： 0.介紹下環境：WIN7 64位 + cygwin32位 + OSG3.2.0 1.首先介紹幾篇博文，參考了不少，但並沒

Android Studio編譯的時候提示Gradle無法下載的解決方案

target 單擊拷貝比較 file 版本編譯 blank 方案首先，打開android studio項目找到項目目錄gradle\wrapper\gradle-wrapper.properties這個文件。內容如下：#Wed Apr 10 15:27:10 PD

加速Android Studio編譯速度

strip roi cache code mage -i ide wid 著作權一、修改運行內存進入項目，菜單欄-help-Edit Custom VM Option Paste_Image.png 添加或修改為： -Xms

android反編譯

adbc nsh cef vfs weixin 反編譯 target get blank 轉自這位老鐵：https://www.jianshu.com/p/f5fadbc7d2f8 https://mp.weixin.qq.com/s?__biz=MzA5MzI3NjE2M

如何在VMware裏安裝android-x86

light let .com .html ini ora review line space 如何在VMware裏安裝android-x86vmware android 遇到的問題系統啟動後進入命令行而沒有界面 1. 進入debug模式 2. 重新加載/

android-x86編譯

相關推薦