d5e069e405
It doesn't make sense to specify a DEVICE_MANIFEST_FILE but the build not including it. The conditional definition of the module makes it problematic to have it listed in the PRODUCT_PACKAGES of a generic mk. Test: build mainline_arm64 + mainline_system_arm64 Change-Id: I40e435ce114263ceabbd373d3d719318c592fc13
28 lines
995 B
Makefile
28 lines
995 B
Makefile
#
|
|
# Copyright (C) 2007 The Android Open Source Project
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
#
|
|
|
|
# This is a generic phone product that isn't specialized for a specific device.
|
|
# It includes the base Android platform.
|
|
|
|
$(call inherit-product, $(SRC_TARGET_DIR)/product/generic_no_telephony.mk)
|
|
$(call inherit-product, $(SRC_TARGET_DIR)/product/telephony.mk)
|
|
|
|
# Overrides
|
|
PRODUCT_BRAND := generic
|
|
PRODUCT_DEVICE := generic
|
|
PRODUCT_NAME := generic
|
|
|
|
$(call enforce-product-packages-exist,)
|