服务器 
首页 > 服务器 > 浏览文章

Centos 64位安装aapt、jdk、tomcat的详细教程

(编辑:jimmy 日期: 2024/11/26 浏览:3 次 )

1、安装jdk

#查看系统自带的jdk
[root@localhost ~]# rpm -qa | grep jdk
java-1.7.0-openjdk-1.7.0.79-2.5.5.4.el6.x86_64
java-1.6.0-openjdk-1.6.0.35-1.13.7.1.el6_6.x86_64
#卸载系统自带openjdk
[root@localhost ~]# rpm -e --nodeps java-1.6.0-openjdk-1.6.0.35-1.13.7.1.el6_6.x86_64
[root@localhost ~]# rpm -e --nodeps java-1.7.0-openjdk-1.7.0.79-2.5.5.4.el6.x86_64
#查看jdk版本
[root@localhost ~]# java -version
-bash: /usr/bin/java: 没有那个文件或目录
#ok,卸载成功!
#下面安装我们自己的jdk
#自己去下载
[root@localhost ~]# cd /usr/local/java/jdk
#查看目录文件
[root@localhost java]# ls
jdk-7u79-linux-x64.tar.gz
#解压
[root@localhost jdk]# tar -zxvf jdk-7u79-linux-x64.tar.gz
#授权
[root@localhost jdk]# chmod +x jdk1.7.0_79/

配置环境变量,(稍后和tomcat一起配置)

2.安装tomcat

下载目录:tomcat7下载地址

#查看
[root@localhost java]# ls tomcat/
apache-tomcat-7.0.29.tar.gz
#解压
[root@localhost tomcat]# tar -zxvf apache-tomcat-7.0.29.tar.gz 
#授权
[root@localhost jdk]# chmod +x apache-tomcat-7.0.29

3、配置环境变量

#编辑profile文件:vim /etc/profile
export JAVA_HOME=/usr/local/java/jdk/jdk1.7.0_79
export CALSSPATH=$JAVA_HOME/lib/*.* 
export PATH=$PATH:$JAVA_HOME/bin 
export TOMCAT_HOME=/usr/local/java/tomcat/apache-tomcat-7.0.29
export CATALINA_HOME=/usr/local/java/tomcat/apache-tomcat-7.0.29
#保存文件并退出!

注意:等号前后没有空格

#使设置立即生效:
[root@localhost jdk]# source /etc/profile
#查看jdk是否安装成功
[root@localhost jdk]# java -version
java version "1.7.0_79"
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)
#成功!
#启动tomcat
[root@localhost bin]# sh /usr/local/java/tomcat/apache-tomcat-7.0.29/bin/startup.sh
#查看启动日志
[root@localhost bin]# tail -f /usr/local/java/tomcat/apache-tomcat-7.0.29/logs/catalina.out
#访问tomcat
http://192.168.81.115:8080/
#如果访问不了,要开启防火墙
#打开防火墙端口命令
#开启8080端口
[root@localhost bin]# /sbin/iptables -I INPUT -p tcp --dport 8080 -j ACCEPT
#再次访问tomcat
http://192.168.81.115:8080/

OK!

4、安装aapt

下载目录:

aapt下载

apktool.jar下载
#授权
[root@localhost apktool]# chmod +x aapt
#执行
[root@localhost apktool]# ./aapt
-bash: ./aapt: /lib/ld-linux.so.2: bad ELF interpreter: 没有那个文件或目录
#那么在64位操作系统下去执行./aapt命令的话会报以上错误
#我们需要安装:glibc.i686,zlib.i686,libstdc++.i686
#(1.)第一步
[root@localhost apktool]# yum install glibc.i686
[root@localhost apktool]# ./aapt
#./aapt: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
#(2.)第二步
[root@localhost apktool]# sudo yum install zlib.i686
[root@localhost apktool]# ./aapt
#./aapt: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
#(3.)第三步
[root@localhost apktool]# sudo yum install libstdc++.i686
#运行./aapt version看看是否安装成功
[root@localhost apktool]# ./aapt version
#Android Asset Packaging Tool, v0.2
#如果出现以上说明安装成功,或者可以执行运行./aapt,如果出现一大坨和最下面的相同的东西说明成功;如果还是报错,就继续往下走
#(4.)第四步
[root@localhost apktool]# ./aapt
#看最后一句
#Protected multilib versions: libstdc++-4.4.7-17.el6.i686 != libstdc++-4.4.7-16.el6.x86_64
#如果报错的话需要升级 != 后面的版本,执行
[root@localhost apktool]# yum update libstdc++-4.4.7-16.el6.x86_64
[root@localhost apktool]# ./aapt
#./aapt: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
#还是报错,继续
#(5.)第五步
[root@localhost apktool]# yum install libstdc++.so.6
[root@localhost apktool]# ./aapt
Android Asset Packaging Tool
Usage:
aapt l[ist] [-v] [-a] file.{zip,jar,apk}
List contents of Zip-compatible archive.
aapt d[ump] [--values] WHAT file.{apk} [asset [asset ...]]
badging Print the label and icon for the app declared in APK.
permissions Print the permissions from the APK.
resources Print the resource table from the APK.
configurations Print the configurations in the APK.
xmltree Print the compiled xmls in the given assets.
xmlstrings Print the strings of the given compiled xml assets.
aapt p[ackage] [-d][-f][-m][-u][-v][-x][-z][-M AndroidManifest.xml] [-0 extension [-0 extension ...]] [-g tolerance] [-j jarfile] [--debug-mode] [--min-sdk-version VAL] [--target-sdk-version VAL] [--app-version VAL] [--app-version-name TEXT] [--custom-package VAL] [--rename-manifest-package PACKAGE] [--rename-instrumentation-target-package PACKAGE] [--utf16] [--auto-add-overlay] [--max-res-version VAL] [-I base-package [-I base-package ...]] [-A asset-source-dir] [-G class-list-file] [-P public-definitions-file] [-S resource-sources [-S resource-sources ...]] [-F apk-file] [-J R-file-dir] [--product product1,product2,...] [raw-files-dir [raw-files-dir] ...]
Package the android resources. It will read assets and resources that are
supplied with the -M -A -S or raw-files-dir arguments. The -J -P -F and -R
options control which files are output.
aapt r[emove] [-v] file.{zip,jar,apk} file1 [file2 ...]
Delete specified files from Zip-compatible archive.
aapt a[dd] [-v] file.{zip,jar,apk} file1 [file2 ...]
Add specified files to Zip-compatible archive.
aapt v[ersion]
Print program version.
Modifiers:
-a print Android-specific data (resources, manifest) when listing
-c specify which configurations to include. The default is all
configurations. The value of the parameter should be a comma
separated list of configuration values. Locales should be specified
as either a language or language-region pair. Some examples:
en
port,en
port,land,en_US
If you put the special locale, zz_ZZ on the list, it will perform
pseudolocalization on the default locale, modifying all of the
strings so you can look for strings that missed the
internationalization process. For example:
port,land,zz_ZZ
-d one or more device assets to include, separated by commas
-f force overwrite of existing files
-g specify a pixel tolerance to force images to grayscale, default 0
-j specify a jar or zip file containing classes to include
-k junk path of file(s) added
-m make package directories under location specified by -J
-u update existing packages (add new, replace older, remove deleted files)
-v verbose output
-x create extending (non-application) resource IDs
-z require localization of resource attributes marked with
localization="suggested"
-A additional directory in which to find raw asset files
-G A file to output proguard options into.
-F specify the apk file to output
-I add an existing package to base include set
-J specify where to output R.java resource constant definitions
-M specify full path to AndroidManifest.xml to include in zip
-P specify where to output public resource definitions
-S directory in which to find resources. Multiple directories will be scanned
and the first match found (left to right) will take precedence.
-0 specifies an additional extension for which such files will not
be stored compressed in the .apk. An empty string means to not
compress any files at all.
--debug-mode
inserts android:debuggable="true" in to the application node of the
manifest, making the application debuggable even on production devices.
--min-sdk-version
inserts android:minSdkVersion in to manifest. If the version is 7 or
higher, the default encoding for resources will be in UTF-8.
--target-sdk-version
inserts android:targetSdkVersion in to manifest.
--max-res-version
ignores versioned resource directories above the given value.
--values
when used with "dump resources" also includes resource values.
--version-code
inserts android:versionCode in to manifest.
--version-name
inserts android:versionName in to manifest.
--custom-package
generates R.java into a different package.
--auto-add-overlay
Automatically add resources that are only in overlays.
--rename-manifest-package
Rewrite the manifest so that its package name is the package name
given here. Relative class names (for example .Foo) will be
changed to absolute names with the old package so that the code
does not need to change.
--rename-instrumentation-target-package
Rewrite the manifest so that all of its instrumentation
components target the given package. Useful when used in
conjunction with --rename-manifest-package to fix tests against
a package that has been renamed.
--product
Specifies which variant to choose for strings that have
product variants
--utf16
changes default encoding for resources to UTF-16. Only useful when API
level is set to 7 or higher where the default encoding is UTF-8.
--non-constant-id
Make the resources ID non constant. This is required to make an R java class
that does not contain the final value but is used to make reusable compiled
libraries that need to access resources.

出现以上信息说明安装成功!

这时可以上传一个apk文件,然后执行解析apk

目录:

执行: ./aapt d badging 1.apk

可以看到结果输出的包名、版本号等等信息都解析出来了。

以上所述是小编给大家介绍的Centos 64位安装aapt、jdk、tomcat的详细教程,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对网站的支持!

上一篇:CloudStack 环境如何重新部署详解
下一篇:CloudStack 创建主存储失败解决方案
一句话新闻
一文看懂荣耀MagicBook Pro 16
荣耀猎人回归!七大亮点看懂不只是轻薄本,更是游戏本的MagicBook Pro 16.
人们对于笔记本电脑有一个固有印象:要么轻薄但性能一般,要么性能强劲但笨重臃肿。然而,今年荣耀新推出的MagicBook Pro 16刷新了人们的认知——发布会上,荣耀宣布猎人游戏本正式回归,称其继承了荣耀 HUNTER 基因,并自信地为其打出“轻薄本,更是游戏本”的口号。
众所周知,寻求轻薄本的用户普遍更看重便携性、外观造型、静谧性和打字办公等用机体验,而寻求游戏本的用户则普遍更看重硬件配置、性能释放等硬核指标。把两个看似难以相干的产品融合到一起,我们不禁对它产生了强烈的好奇:作为代表荣耀猎人游戏本的跨界新物种,它究竟做了哪些平衡以兼顾不同人群的各类需求呢?
友情链接:杰晶网络 DDR爱好者之家 南强小屋 黑松山资源网 白云城资源网 网站地图 SiteMap