On Thu, Feb 19, 2009 at 11:07 AM, Dianne Hackborn <[email protected]> wrote:
> 2 would be best, but currently we don't support shared libraries with
> resources so you can't really do it.
>
> In cupcake you can define PRODUCT_PACKAGE_OVERLAYS in your product makefile
> to specify one or more directories that will be merged in with the base
> platform directories.
Glad to see this overlay mechanism. Very nice.
How can I test this?
I created a vendor/mycompany/mycompany.mk
------------
PRODUCT_PACKAGES := \
VoiceDialer
# Try adding a product with VoiceDialer
# Superclass
$(call inherit-product, build/target/product/generic.mk)
# Overrides
PRODUCT_BRAND := mybrand
PRODUCT_NAME := myproduct
PRODUCT_DEVICE := mydevice
PRODUCT_MANUFACTURER := me
------------
and a AndroidProducts.mk at the same location
------------
PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/mycompany.mk
------------
But before adding overlays, I tried to do a build but I am not sure
whats the correct target.
make myproduct
make PRODUCT-myproduct-eng
all fails with msg: "No rule to make target"
Is there an example product makefile?
documents/pointers/tips would help.
thanks
Jey
For example:
>
> PRODUCT_PACKAGE_OVERLAYS := vendor/mycompany/prod_overlay
> vendor/mycompany/base_overlay
>
> Now you can replace or add framework resources by putting them in either of
> these:
>
> vendor/mycompany/base_overlay/frameworks/base/core/res/res/
> vendor/mycompany/prod_overlay/frameworks/base/core/res/res/
>
> You can use this to replace any resource in the tree, both in the framework
> and in specific packages, by just putting them in a directory corresponding
> to the same path where you find them in the platform tree.
>
> Also when adding new resources to the frameworks that you want to use in
> your own apps that are built into the system image, you can use the magic
> syntax "@*android:type/name" to reference them without having to make them
> public. You can likewise find private resources in Java at
> com.android.internal.R.
>
> On Thu, Feb 19, 2009 at 12:05 AM, cht <[email protected]> wrote:
>>
>> may be there are someways:
>> 1: put their own resources under the folder "frameworks\base\core
>> \res", mix with android's original resources, although it works, but
>> idont think it is a best way?
>> 2: make their own resource apk like "framework-res.apk", it can
>> separate their own resources from android's original res, but i don't
>> kown how to implements it, and i don't kown whether it is feasible.
>> 3: some else?
>>
>> i think the second is the best, but i don't kown how to implements
>> it.
>>
>> cht
>> thanks
>>
>
>
>
> --
> Dianne Hackborn
> Android framework engineer
> [email protected]
>
> Note: please don't send private questions to me, as I don't have time to
> provide private support. All such questions should be posted on public
> forums, where I and others can see and answer them.
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"android-framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---
