Book Image

Android High Performance Programming

By : Emil Atanasov, Enrique López Mañas, Diego Grancini
Book Image

Android High Performance Programming

By: Emil Atanasov, Enrique López Mañas, Diego Grancini

Overview of this book

Performant applications are one of the key drivers of success in the mobile world. Users may abandon an app if it runs slowly. Learning how to build applications that balance speed and performance with functionality and UX can be a challenge; however, it's now more important than ever to get that balance right. Android High Performance will start you thinking about how to wring the most from any hardware your app is installed on, so you can increase your reach and engagement. The book begins by providing an introduction to state–of-the-art Android techniques and the importance of performance in an Android application. Then, we will explain the Android SDK tools regularly used to debug and profile Android applications. We will also learn about some advanced topics such as building layouts, multithreading, networking, and security. Battery life is one of the biggest bottlenecks in applications; and this book will show typical examples of code that exhausts battery life, how to prevent this, and how to measure battery consumption from an application in every kind of situation to ensure your apps don’t drain more than they should. This book explains techniques for building optimized and efficient systems that do not drain the battery, cause memory leaks, or slow down with time.
Table of Contents (17 chapters)
Android High Performance Programming
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
Index

NDK macros


Macros are small functions that contain a particular functionality. A few of them are defined by default by NDK. To call them, you must use the following syntax:

$(call <function-name>)

Here are a few of the default macros specified in the NDK:

  • my-dir: This macro returns the current path of the Android.mk file. It can be very useful when, initially, you want to set up LOCAL_PATH in the script:

    LOCAL_PATH := $(call my-dir)
    all-subdir-makefiles

    When this macro is executed, it returns as a list all the Android.mk makefiles that have been found in the folder returned by my-dir.

    By using this command, we can provide a better line of sub hierarchies and a better organization of the package structure.

  • parent-makefile: This returns the path where the parent makefile can be found.

    Tip

    The command grand-parent-makefile also exists, and it returns, as obviously inferred, the path of the grandparent.

  • this-makefile: This macro returns the path of the current makefile.