2010-06-16 18:44:05 -07:00
|
|
|
LOCAL_PATH:= $(call my-dir)
|
|
|
|
|
include $(CLEAR_VARS)
|
|
|
|
|
|
2010-08-08 00:14:31 -07:00
|
|
|
# Only build libhwui when USE_OPENGL_RENDERER is
|
|
|
|
|
# defined in the current device/board configuration
|
|
|
|
|
ifeq ($(USE_OPENGL_RENDERER),true)
|
|
|
|
|
LOCAL_SRC_FILES:= \
|
2013-03-08 11:28:22 -08:00
|
|
|
utils/Blur.cpp \
|
2010-10-08 15:49:53 -07:00
|
|
|
utils/SortedListImpl.cpp \
|
2013-03-11 20:48:31 -07:00
|
|
|
thread/TaskManager.cpp \
|
2012-09-04 12:55:44 -07:00
|
|
|
font/CacheTexture.cpp \
|
|
|
|
|
font/Font.cpp \
|
Pack preloaded framework assets in a texture atlas
When the Android runtime starts, the system preloads a series of assets
in the Zygote process. These assets are shared across all processes.
Unfortunately, each one of these assets is later uploaded in its own
OpenGL texture, once per process. This wastes memory and generates
unnecessary OpenGL state changes.
This CL introduces an asset server that provides an atlas to all processes.
Note: bitmaps used by skia shaders are *not* sampled from the atlas.
It's an uncommon use case and would require extra texture transforms
in the GL shaders.
WHAT IS THE ASSETS ATLAS
The "assets atlas" is a single, shareable graphic buffer that contains
all the system's preloaded bitmap drawables (this includes 9-patches.)
The atlas is made of two distinct objects: the graphic buffer that
contains the actual pixels and the map which indicates where each
preloaded bitmap can be found in the atlas (essentially a pair of
x and y coordinates.)
HOW IS THE ASSETS ATLAS GENERATED
Because we need to support a wide variety of devices and because it
is easy to change the list of preloaded drawables, the atlas is
generated at runtime, during the startup phase of the system process.
There are several steps that lead to the atlas generation:
1. If the device is booting for the first time, or if the device was
updated, we need to find the best atlas configuration. To do so,
the atlas service tries a number of width, height and algorithm
variations that allows us to pack as many assets as possible while
using as little memory as possible. Once a best configuration is found,
it gets written to disk in /data/system/framework_atlas
2. Given a best configuration (algorithm variant, dimensions and
number of bitmaps that can be packed in the atlas), the atlas service
packs all the preloaded bitmaps into a single graphic buffer object.
3. The packing is done using Skia in a temporary native bitmap. The
Skia bitmap is then copied into the graphic buffer using OpenGL ES
to benefit from texture swizzling.
HOW PROCESSES USE THE ATLAS
Whenever a process' hardware renderer initializes its EGL context,
it queries the atlas service for the graphic buffer and the map.
It is important to remember that both the context and the map will
be valid for the lifetime of the hardware renderer (if the system
process goes down, all apps get killed as well.)
Every time the hardware renderer needs to render a bitmap, it first
checks whether the bitmap can be found in the assets atlas. When
the bitmap is part of the atlas, texture coordinates are remapped
appropriately before rendering.
Change-Id: I8eaecf53e7f6a33d90da3d0047c5ceec89ea3af0
2013-04-17 18:54:38 -07:00
|
|
|
AssetAtlas.cpp \
|
2010-08-08 00:14:31 -07:00
|
|
|
FontRenderer.cpp \
|
2010-08-26 20:35:23 -07:00
|
|
|
GammaFontRenderer.cpp \
|
2010-10-22 18:59:26 -07:00
|
|
|
Caches.cpp \
|
2013-02-14 15:36:01 -08:00
|
|
|
DisplayList.cpp \
|
2013-02-04 16:16:33 -08:00
|
|
|
DeferredDisplayList.cpp \
|
2011-03-24 10:51:31 -07:00
|
|
|
DisplayListLogBuffer.cpp \
|
2010-10-18 14:06:08 -07:00
|
|
|
DisplayListRenderer.cpp \
|
2012-07-31 21:16:07 -07:00
|
|
|
Dither.cpp \
|
2013-02-06 16:51:04 -08:00
|
|
|
Extensions.cpp \
|
2010-10-18 14:06:08 -07:00
|
|
|
FboCache.cpp \
|
2010-08-08 00:14:31 -07:00
|
|
|
GradientCache.cpp \
|
2013-05-02 17:50:23 -07:00
|
|
|
Image.cpp \
|
2012-09-05 11:40:29 -07:00
|
|
|
Layer.cpp \
|
2010-08-08 00:14:31 -07:00
|
|
|
LayerCache.cpp \
|
2011-01-11 14:29:25 -08:00
|
|
|
LayerRenderer.cpp \
|
2010-08-08 00:14:31 -07:00
|
|
|
Matrix.cpp \
|
|
|
|
|
OpenGLRenderer.cpp \
|
|
|
|
|
Patch.cpp \
|
|
|
|
|
PatchCache.cpp \
|
|
|
|
|
PathCache.cpp \
|
2012-12-10 17:56:27 -08:00
|
|
|
PathTessellator.cpp \
|
2013-04-08 19:40:31 -07:00
|
|
|
PixelBuffer.cpp \
|
2010-08-08 00:14:31 -07:00
|
|
|
Program.cpp \
|
|
|
|
|
ProgramCache.cpp \
|
2013-02-12 16:08:55 -08:00
|
|
|
RenderBufferCache.cpp \
|
2010-10-08 08:37:55 -07:00
|
|
|
ResourceCache.cpp \
|
2010-08-08 00:14:31 -07:00
|
|
|
SkiaColorFilter.cpp \
|
|
|
|
|
SkiaShader.cpp \
|
2012-02-02 17:31:16 -08:00
|
|
|
Snapshot.cpp \
|
2012-08-31 20:31:01 -07:00
|
|
|
Stencil.cpp \
|
2013-06-04 18:00:09 -07:00
|
|
|
Texture.cpp \
|
2010-08-13 19:39:53 -07:00
|
|
|
TextureCache.cpp \
|
|
|
|
|
TextDropShadowCache.cpp
|
2012-09-17 17:25:49 -07:00
|
|
|
|
2013-02-13 16:14:17 -08:00
|
|
|
intermediates := $(call intermediates-dir-for,STATIC_LIBRARIES,libRS,TARGET,)
|
|
|
|
|
|
2010-08-08 00:14:31 -07:00
|
|
|
LOCAL_C_INCLUDES += \
|
|
|
|
|
$(JNI_H_INCLUDE) \
|
|
|
|
|
$(LOCAL_PATH)/../../include/utils \
|
|
|
|
|
external/skia/include/core \
|
|
|
|
|
external/skia/include/effects \
|
|
|
|
|
external/skia/include/images \
|
2012-08-14 16:44:52 -04:00
|
|
|
external/skia/src/core \
|
2010-08-08 00:14:31 -07:00
|
|
|
external/skia/src/ports \
|
2013-03-28 18:10:43 -07:00
|
|
|
external/skia/include/utils
|
2010-06-22 13:11:24 -07:00
|
|
|
|
Pack preloaded framework assets in a texture atlas
When the Android runtime starts, the system preloads a series of assets
in the Zygote process. These assets are shared across all processes.
Unfortunately, each one of these assets is later uploaded in its own
OpenGL texture, once per process. This wastes memory and generates
unnecessary OpenGL state changes.
This CL introduces an asset server that provides an atlas to all processes.
Note: bitmaps used by skia shaders are *not* sampled from the atlas.
It's an uncommon use case and would require extra texture transforms
in the GL shaders.
WHAT IS THE ASSETS ATLAS
The "assets atlas" is a single, shareable graphic buffer that contains
all the system's preloaded bitmap drawables (this includes 9-patches.)
The atlas is made of two distinct objects: the graphic buffer that
contains the actual pixels and the map which indicates where each
preloaded bitmap can be found in the atlas (essentially a pair of
x and y coordinates.)
HOW IS THE ASSETS ATLAS GENERATED
Because we need to support a wide variety of devices and because it
is easy to change the list of preloaded drawables, the atlas is
generated at runtime, during the startup phase of the system process.
There are several steps that lead to the atlas generation:
1. If the device is booting for the first time, or if the device was
updated, we need to find the best atlas configuration. To do so,
the atlas service tries a number of width, height and algorithm
variations that allows us to pack as many assets as possible while
using as little memory as possible. Once a best configuration is found,
it gets written to disk in /data/system/framework_atlas
2. Given a best configuration (algorithm variant, dimensions and
number of bitmaps that can be packed in the atlas), the atlas service
packs all the preloaded bitmaps into a single graphic buffer object.
3. The packing is done using Skia in a temporary native bitmap. The
Skia bitmap is then copied into the graphic buffer using OpenGL ES
to benefit from texture swizzling.
HOW PROCESSES USE THE ATLAS
Whenever a process' hardware renderer initializes its EGL context,
it queries the atlas service for the graphic buffer and the map.
It is important to remember that both the context and the map will
be valid for the lifetime of the hardware renderer (if the system
process goes down, all apps get killed as well.)
Every time the hardware renderer needs to render a bitmap, it first
checks whether the bitmap can be found in the assets atlas. When
the bitmap is part of the atlas, texture coordinates are remapped
appropriately before rendering.
Change-Id: I8eaecf53e7f6a33d90da3d0047c5ceec89ea3af0
2013-04-17 18:54:38 -07:00
|
|
|
LOCAL_CFLAGS += -DUSE_OPENGL_RENDERER -DEGL_EGLEXT_PROTOTYPES -DGL_GLEXT_PROTOTYPES
|
2010-08-08 00:14:31 -07:00
|
|
|
LOCAL_MODULE_CLASS := SHARED_LIBRARIES
|
Pack preloaded framework assets in a texture atlas
When the Android runtime starts, the system preloads a series of assets
in the Zygote process. These assets are shared across all processes.
Unfortunately, each one of these assets is later uploaded in its own
OpenGL texture, once per process. This wastes memory and generates
unnecessary OpenGL state changes.
This CL introduces an asset server that provides an atlas to all processes.
Note: bitmaps used by skia shaders are *not* sampled from the atlas.
It's an uncommon use case and would require extra texture transforms
in the GL shaders.
WHAT IS THE ASSETS ATLAS
The "assets atlas" is a single, shareable graphic buffer that contains
all the system's preloaded bitmap drawables (this includes 9-patches.)
The atlas is made of two distinct objects: the graphic buffer that
contains the actual pixels and the map which indicates where each
preloaded bitmap can be found in the atlas (essentially a pair of
x and y coordinates.)
HOW IS THE ASSETS ATLAS GENERATED
Because we need to support a wide variety of devices and because it
is easy to change the list of preloaded drawables, the atlas is
generated at runtime, during the startup phase of the system process.
There are several steps that lead to the atlas generation:
1. If the device is booting for the first time, or if the device was
updated, we need to find the best atlas configuration. To do so,
the atlas service tries a number of width, height and algorithm
variations that allows us to pack as many assets as possible while
using as little memory as possible. Once a best configuration is found,
it gets written to disk in /data/system/framework_atlas
2. Given a best configuration (algorithm variant, dimensions and
number of bitmaps that can be packed in the atlas), the atlas service
packs all the preloaded bitmaps into a single graphic buffer object.
3. The packing is done using Skia in a temporary native bitmap. The
Skia bitmap is then copied into the graphic buffer using OpenGL ES
to benefit from texture swizzling.
HOW PROCESSES USE THE ATLAS
Whenever a process' hardware renderer initializes its EGL context,
it queries the atlas service for the graphic buffer and the map.
It is important to remember that both the context and the map will
be valid for the lifetime of the hardware renderer (if the system
process goes down, all apps get killed as well.)
Every time the hardware renderer needs to render a bitmap, it first
checks whether the bitmap can be found in the assets atlas. When
the bitmap is part of the atlas, texture coordinates are remapped
appropriately before rendering.
Change-Id: I8eaecf53e7f6a33d90da3d0047c5ceec89ea3af0
2013-04-17 18:54:38 -07:00
|
|
|
LOCAL_SHARED_LIBRARIES := liblog libcutils libutils libEGL libGLESv2 libskia libui
|
2010-08-08 00:14:31 -07:00
|
|
|
LOCAL_MODULE := libhwui
|
|
|
|
|
LOCAL_MODULE_TAGS := optional
|
2012-07-17 17:32:48 -07:00
|
|
|
|
2013-04-16 11:30:05 -07:00
|
|
|
ifneq (false,$(ANDROID_ENABLE_RENDERSCRIPT))
|
|
|
|
|
LOCAL_CFLAGS += -DANDROID_ENABLE_RENDERSCRIPT
|
|
|
|
|
LOCAL_SHARED_LIBRARIES += libRS libRScpp
|
|
|
|
|
LOCAL_C_INCLUDES += \
|
|
|
|
|
$(intermediates) \
|
|
|
|
|
frameworks/rs/cpp \
|
|
|
|
|
frameworks/rs
|
|
|
|
|
endif
|
2013-03-28 18:10:43 -07:00
|
|
|
|
2012-07-17 17:32:48 -07:00
|
|
|
ifndef HWUI_COMPILE_SYMBOLS
|
|
|
|
|
LOCAL_CFLAGS += -fvisibility=hidden
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
ifdef HWUI_COMPILE_FOR_PERF
|
|
|
|
|
LOCAL_CFLAGS += -fno-omit-frame-pointer -marm -mapcs
|
|
|
|
|
endif
|
|
|
|
|
|
2010-08-08 00:14:31 -07:00
|
|
|
include $(BUILD_SHARED_LIBRARY)
|
2010-06-16 18:44:05 -07:00
|
|
|
|
2013-02-13 16:14:17 -08:00
|
|
|
include $(call all-makefiles-under,$(LOCAL_PATH))
|
2010-08-08 00:14:31 -07:00
|
|
|
endif
|
