使用Android构建与移植经典游戏

需积分: 4 134 浏览量更新于2024-08-02 收藏 3.56MB PDF 举报

"Apress.Pro.Android.Games.2009.pdf 是一本专注于Android游戏开发的专业书籍，由Vladimir Silva撰写。这本书涵盖了从零开始构建Java游戏，利用OpenGL和JNI混合开发3D图形，以及将经典游戏如Wolfenstein 3D和Doom移植到Android平台的详细步骤。书中还提供了部署和编译的提示，适合中级至高级水平的开发者。" 本书详细介绍了Android游戏开发的多个关键知识点： 1. **欢迎来到Android游戏**：这部分可能涵盖了Android游戏市场的概述，包括其潜力、用户基础和开发环境的介绍。它可能引导读者了解Android SDK和Android Studio，为后续章节打下基础。 2. **在Android中编译原生代码**：这一章讨论了如何使用NDK（Native Development Kit）来编写和集成C/C++代码，这在处理高性能计算或游戏引擎时非常有用。NDK允许开发者利用C和C++的效率，同时与Java环境交互。 3. **从头构建Java游戏**：这一部分深入讲解了使用Java进行游戏开发的基础，包括游戏循环、碰撞检测、动画和用户输入处理等核心概念。作者可能会提供一个简单的游戏示例来展示这些概念的实际应用。 4. **Java游戏进阶：多边形的乐趣**：此章节可能进一步探讨了2D图形和几何，如何创建复杂的形状和场景，以及如何利用Android的图形库优化性能。 5. **混合3D图形：OpenGL和JNI**：OpenGL ES是Android上实现3D图形的主要API，JNI（Java Native Interface）则允许Java代码调用C/C++函数。这一章可能解释了如何结合两者来实现高效的3D游戏渲染。 6. **3D射击游戏第一集：Android上的Wolfenstein 3D**：这个章节详细指导如何将Wolfenstein 3D游戏移植到Android，涉及纹理映射、视角控制和3D对象的移动。 7. **3D射击游戏第二集：Android上的Doom**：类似于前一章，本章将涵盖Doom游戏的移植技术，可能包括更复杂的游戏逻辑、网络对战支持和资源管理。 8. **附录：部署和编译技巧**：这部分提供了实用的建议，帮助开发者解决在构建和发布游戏过程中可能遇到的问题，例如签名证书的创建、APK的打包和调试技巧。 9. **索引**：书末的索引方便读者查找特定主题和技术。通过这本书，读者可以掌握在Android平台上开发游戏的全面技能，从简单的2D游戏到复杂的3D移植项目，同时也了解到如何利用Java和原生代码的优势来优化游戏性能。无论是对游戏开发感兴趣的新手还是有经验的开发者，都能从中受益。

■ INTRODUCTION

xiv

GNU C Compiler for ARM Processors

A GNU C compiler is required for the hybrid games in the book. These games combine Java code with a

native core library, hence the need for a C compiler that targets the mobile ARM processor. The compiler

used in this book and detailed in Chapter 1 is the Code Sourcery GNU G++ Toolkit. You are not bound,

however, to use this compiler; as a matter of fact, you can use any C compiler capable of generating ARM

code, including the Android Native Development Kit (NDK).

Chapter Source

This is an optional tool but it will help you greatly to understand the concepts as you move along. I have

made my best effort to describe each chapter as simply as possible. Nevertheless, some of the games

(especially Wolf 3D and Doom) have very large core engines written in C (100K lines for Doom), which

are poorly commented and very hard to understand. All in all you will see how easily these great

languages (Java and C) can be combined with minimal effort. Get the companion source for the book

from the publisher at http://www.apress.com. It was built using Eclipse Galileo.

What Makes This Book Unique?

I think it is important for the reader to understand my goal with this manuscript and what I believe sets

this book apart. Even though Java is the primary development language for Android, Google has realized

the need for hybrid Java/C development if Android is to succeed as a gaming platform, so much so that

they released the Native Development Kit (NDK). Google is realizing the need to support C development

to catch up with the overwhelming number of native games written for other mobile platforms like the

iPhone. PC games have been around for decades (mostly written in C), and by using a simple ARM C

compiler, you could potentially bring thousands of PC games to the Android Platform. This is what

makes this book unique. Why translate 100k lines of painfully complicated code from C to Java if you can

just combine both languages in an elegant manner with significant savings on time and money? My

book will help you to do just that. This is my goal and what makes this book stand out. In the other hand,

this book also includes chapters of pure Java games in a well-balanced layout to satisfy both the Java

purist and the C lover in you.

Android SDK Compatibility

As a developer you may ask yourself about the SDK compatibility of the code in this book. This is an

important question as new versions of the Android SDK come out frequently. By the time of this writing,

Google released the Android SDK version 2.0. The code in this chapter has been tested with the following

versions of the Android SDK:

• SDK version 2.0

• SDK version 1.6

• SDK version 1.5

• SDK version 1.0

■ INTRODUCTION

The bottom line is that the code in this book will run in any version of the SDK from 2.0 to 1.0, and that

was my intention all along.

SDK Changes for Version 1.6

Virtually nothing has changed from versions 1.5 to 1.6 of the platform when it comes to game

development. For a detailed list of API changes in version 1.6, see

http://developer.android.com/sdk/RELEASENOTES.html.

This book has a well-balanced layout of pure Java and hybrid games, divided as follows:

Chapter 1

This chapter provides the first step to set up a Linux system for hybrid game compilation, including

fetching the Android source, extracting device system libraries, setting up a custom compilation

toolchain, custom compilation scripts, plus details on setting up the Eclipse IDE for use throughout the

rest of the book.

Chapter 2

In this chapter you will learn how to combine Java and C code in an elegant manner by building a simple

Java application on top of a native library. You will learn exciting concepts about the Java Native

Interface (JNI) and the API used to combine Java and C in a single unit, including how to load native

libraries, how to use the native keyword, how to generate the JNI headers, plus all about method

signatures, Java arrays vs. C arrays, invoking Java methods, compiling and packing the product, and

more.

Chapter 3

This chapter is the first in a series to explore pure Java gaming with a real-world game dubbed Space

Blaster. The goal of this game is to maneuver (using your finger tips or the keyboard) a space ship

through a field of meteors. This chapter will teach you how to build custom XML-based linear layout,

how to use an abstract class and timer tasks to simulate a simple game loop, how to invalidate views

within a non-UI thread, how to load sprites and sounds from the project resources, plus drawing

techniques such as sprite animations, drawing simple objects, and setting style and color using the Paint

object.

Chapter 4

Pure Java games continue in Chapter 4 with the arcade classic Asteroids. This chapter will teach you all

about drawing polygon sprites on the Android canvas. This is a somewhat difficult technique due to the

lack of polygon support in the Android API. The chapter relies on the high portability of the Java

language to bring polygon code from the J2SE API into the Android API to ultimately create Asteroids. As

■ INTRODUCTION

xvi

you may have noticed, this is a mostly Polygon-based game. Other interesting topics include game life

cycle steps, initialization, draw, and update physics, responding to key and touch events, plus testing on

the device emulator.

Chapter 5

This chapter deals with 3D graphics with OpenGL. It presents a neat trick I stumbled on by coincidence

that allows for mixing OpenGL API calls in both Java and C. This concept is illustrated by using the 3D

cubes sample provided by Google to demonstrate OpenGL in pure Java and hybrid modes. This trick

could open a new frontier of 3D development for Android with the potential to bring a large number of

3D PC games to the platform with enormous savings in development costs and time.

Chapter 6

This is the first chapter in a series of two, which are my personal favorites of this book. Here it brings the

godfather of all PC 3D shooters to the Android platform—Wolfenstein 3D. Who would have thought that

a PC game like this one could be brought to an Android mobile device with minimal effort? This chapter

demonstrates how Java and C can coexist harmoniously and includes topics such as the basic game

architecture (showing how the Java and C components fit together), resource handlers for sound, music,

key and touch events, how to use JNI to cascade graphics information, video buffers, and sound/music

requests back to Java, plus compilation and testing.

Chapter 7

Chapter 7 takes things to the next level with the ground-breaking game for the PC—Doom. Doom is

arguably the greatest 3D game ever created and opened new frontiers in 3D graphics. The ultimate goal

of this chapter is not to describe the game itself, but to show you how easy it is to bring a complex PC

game like Doom to the Android platform. The proof? Doom is 100+K lines of C code and brought to

Android with less than 200 lines of extra JNI API calls, plus the Java code required to build the mobile UI.

This chapter shows that you don’t have to translate 100K lines of C into Java but simply marry these two

powerful languages in an elegant application. Consider the potential savings in development time and

costs! This chapter is a must-read.

C H A P T E R 1

■ ■ ■

Welcome to Android Gaming

Welcome to the world of Android Games! The goal of this book is to help you build the best games for the

platform. As you work your way through the chapters, you will learn how to create two kinds of games:

pure Java, and perhaps most interestingly, hybrid games that combine the elegant design of Java with

the raw power of C for maximum performance. The ability to combine both Java and C in this way is

what makes the games in this book unique, as Google does not support this kind of development. But

you may ask, “Why even bother with hybrid games?” After all, Java provides all the APIs you need to

build any kind of game. This is certainly true. However, there are thousands of games out there written

in C that can be brought to Android by compiling the C core and wrapping a Java graphical user

interface (GUI) using the Java Native Interface (JNI). In this book, you’ll learn how to bring to the

platform two of the great 3D shooter games for the PC: Wolfenstein 3D and Doom.

The bottom line? My goal is to bring to you the latest documented and undocumented secrets to

building games for Android. Furthermore, if your plan is to port a PC game, this book will provide you

with invaluable expertise to do so. But before we get started, there are some things you need to know to

get the most from this book.

What Skills Do You Need?

In this book, I am targeting seasoned game developers, not only in Java, but also in C. This makes sense,

as performance is critical in game development. Java provides elegant object-oriented capabilities, but

only C gives you the power boost that game development needs. This is the best of both worlds in the

palm of your hand. This book assumes you are familiar with Android, as well as Linux and shell scripting.

A Solid Foundation of Android

This book assumes that you already know the basics of Android development. For example, you need to

know what activities, views, and layouts are. Consider the following fragment. If you understand what it

does just by looking at it, then you are in good shape.

public class MainActivity extends Activity

{

public void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);

setContentView(R.layout.main);

CHAPTER 1 ■ WELCOME TO ANDROID GAMING

}

This fragment defines the main activity or class that controls the life cycle of the application. The

onCreate method will be called once when the application starts, and its job is to set the content layout

or GUI for the application.

You should also have a basic understanding of how GUIs are created using XML. Look at the next

fragment. Can you tell what it does?

<?xml version="1.0" encoding="utf-8"?>

<RelativeLayout

xmlns:android="http://schemas.android.com/apk/res/android"

android:layout_width="fill_parent"

android:layout_height="fill_parent">

<ImageView android:id="@+id/doom_iv"

android:layout_width="fill_parent"

android:layout_height="fill_parent"

android:background="@drawable/doom"

android:focusableInTouchMode="true" android:focusable="true"/>

<ImageButton android:id="@+id/btn_upleft"

android:layout_width="wrap_content"

android:layout_height="wrap_content"

android:layout_alignParentBottom="true"

android:layout_alignParentLeft="true"

android:src="@drawable/img1" />

</RelativeLayout>

This code defines a relative layout. In a relative layout, widgets are placed relative to each other

(sometimes overlapping). In this case, there is an image view that fills the entire screen. This image will

display as the background the file called doom.png stored in the res/drawable folder of the project, and

receive key and touch events. In the lower left of the screen, overlapping the image view, an image

button with the ID btn_upleft will be displayed.

Need an Android Tutorial?

There are a lot of concepts related to Android development, and it is impossible to remember every detail

about activities, views, and layouts. A handy place to access this information quickly is the Android tutorial:

http://developer.android.com/

The ultimate guide for Android developers—the latest releases, downloads, SDK Quick Start, version

notes, native development tools, and previous releases—can be found here:

http://developer.android.com/sdk/1.6_r1/index.html

Throughout this book (especially in the chapters dealing with native code), I make extensive use of

the Android Software Development Kit (SDK) command tools (for system administrator tasks). Thus,

剩余316页未读，继续阅读

rootfs

粉丝: 21
资源: 146

使用Android构建与移植经典游戏

Apress.Pro.Android.Games.2Ed.2012

[android.开发书籍].Apress.Pro.Android.Media.Dec.2010.pdf

Apress.Pro OpenGL ES for Android.2012

关于springboot的英文文献

帮我找一下可以写再javaweb毕设里的英文参考文献

spring boot项目英文文献

javascript相关外文文献

列举几个SpringBoot相关的技术文献,以文献引用的格式展示

springboot的参考文献

springboot框架外文参考文献列表

最新资源