Removing external components in Android Build

by AJAY » Tue, 17 Feb 2009 07:50:47 GMT


Sponsored Links
 Hi,

Is  there anyway I can exclude certain external libraries/components
which I am not testing  like webkit during the Android build. I want
to speed up my build process during development. I see that making
changes in build/target/product/core.mk also has no effect.

This is because I see that after making certain changes to the code,
say PV  omx components , the change doesnt get reflected unless I do a
make clean.


--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Removing external components in Android Build

by David Turner » Tue, 17 Feb 2009 08:38:47 GMT


 This is not supposed to happen. What kind of change are you talking about ?
Sounds like a build system bug. You should not have to rebuild Webkit if you
change something that is unrelated.

For the record, you can still use standard GNU Make -B option to mm or mmm
to force a rebuild
without having to do a 'make clean'






--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---


Sponsored Links


Other Threads

1. How to handle this kind of situation within my code

Also in the original scenario, your service was NOT running in the
background -- its onDestroy() was called, and you ignored it and continued
doing stuff. :)  Your process will happen to stick around for some time
after that in case it is needed again, but the system will fairly
aggressively kill an empty process like that for memory, so you are living
on borrowed time.

On Tue, Aug 25, 2009 at 1:02 PM, Streets Of Boston









-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

--~--~---------~--~----~------------~-------~--~----~

2. How to handle this kind of situation within my code

Hey guys,
I was wondering on this for quite a bit but couldn't find any
solution!

1. My app bind to a service (through AIDL interface)
2, The service runs in the backround and send to my activity a value
every now and than (and also a notification is sent)

When I click the HOME button, and than navigate back to my application
(while still i get notifications) to my app and launch it, everything
is fine, i'm back to my app as if I never left it (i get a window with
my value displayed)

When I click the BACK button the service dies along with the activity
that is bound to it (the onDestroy() of the service is fired and the
code there removes all the messages)

now, I removed the code that disabled the message handler to my
services, and the service is kept a live even if i killed the host
activity.

however, the service still runs in the bk and i get notifications but
when I run my activity again, it wants to start a new service! which
means, the service in the background is left to run without any
binding to it, and it just there in the void running.

my question:
How mp3 alike apps in android catch the BACK button and still able to
keep connection to a service even after the activity is closed?

i can save the process ID of the service, but is it possible to attach
your self to the service? or even re-bind to the existing one?

how does it work??
thanx!

--~--~---------~--~----~------------~-------~--~----~

3. Take a Picture without an Activity

4. How come the accelrometers maximum sampling rate are so low?

5. Emulator quick start

6. Color tolerance in a 9-patch border

7. What's the meaning of the $ (dollar sign) in the backtrace?