Book Image

Mastering Android NDK

Book Image

Mastering Android NDK

Overview of this book

Android NDK is used for multimedia applications that require direct access to system resources. NDK is also the key for portability, which in turn allows a reasonably comfortable development and debugging process using familiar tools such as GCC and Clang toolchains. This is a hands-on guide to extending your game development skills with Android NDK. The book takes you through many clear, step-by-step example applications to help you further explore the features of Android NDK and some popular C++ libraries and boost your productivity by debugging the development process. Through the course of this book, you will learn how to write portable multi-threaded native code, use HTTP networking in C++, play audio files, use OpenGL ES 3, and render high-quality text. Each chapter aims to take you one step closer to building your application. By the end of this book, you will be able to create an engaging, complete gaming application.
Table of Contents (17 chapters)
Mastering Android NDK
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Task queues


To process a logical piece of work, we will declare the iTask class with the Run() method, which can perform a time-consuming operation. The declaration of the class is somewhat visually similar to iThread. However, its instances implement some reasonably short operation and may be executed in different threads:

  class iTask: public iIntrusiveCounter
  {
  public:
    iTask()
    : FIsPendingExit( false )
    , FTaskID( 0 )
    , FPriority( 0 )
    {};

The pure virtual method Run() should be overridden in subclasses to do the actual work:

    virtual void Run() = 0;

The following methods optionally cancel the task and are similar to the ones in the iThread class. Their purpose is to signal the hosting thread that this task should be cancelled:

    virtual void Exit()
    {
      FIsPendingExit = true;
    }
    virtual bool IsPendingExit() const volatile
    {
      return FIsPendingExit;
    }

The GetTaskID() and SetTaskID() methods access the internal unique identifier of the task...