Android.mk and chmod

by Hamilton Vera » Sat, 17 Jul 2010 01:37:47 GMT


Sponsored Links
 Greetings everyone.

We are porting a hardware to Android and we will need to execute a
script to activate its module, here is the Android.mk:

LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)


file := $(TARGET_OUT)/etc/init.modem.sh
$(file) : $(LOCAL_PATH)/init.modem.sh | $(ACP)
        $(transform-prebuilt-to-target)
        $(hide) chmod 0777 $@
ALL_PREBUILT += $(file)

Unfortunately when the image is built the file does not inherit the
permissions set in Android.mk .

I want to avoid using chmod in init.rc (to keep it fast and simple), I
am reading ANDROID-MK.TXT, but no luck yet.

I would appreciate any help.

-- 
Hamilton Vera
int Administrator (char Network[],char ComputationalSystems[])
 http://hvera.wordpress.com 

--



Other Threads

1. DDMS doesn't show my G1

I've been working at this for hours now, and I can't figure out what's
going wrong.  I've got USB debugging turned on, I have eclipse, I have
android-sdk-1.6, but when I click ddms.bat, I get a blank command
prompt, and Dalvik Debug Monitor comes up, but it doesn't show any
devices at all.

I'm on Windows XP 32 bit.  What could I be doing wrong?

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

2. Mutex issues.. :(

Could someone point me to the right place?

Here is the pseudo code:

Mutex mx = new Mutex();

public void TurnLightsOff()
{
  if (mx.aquire(ID_1) == false)
  {
    // run some code
    mx.release();
  }
}

public void TurnLightsOn()
{
  if (mx.aquire(ID_2) == false)
  {
    // run some code
    mx.release();
  }
}

If the user calls TurnLightsOff() multiple times it will only take the
first request if ID_1 is on the queue and ignore the rest of the
aquire request since it is already in the line waiting for the
aquire...  I don't want to pile up aquires of the same request
TurnLightsOff() function...  How can I do this? I can't think of the
name for this type of mutex scenarios...

Thanks in advance..
-Moto
--~--~---------~--~----~------------~-------~--~----~

3. ProximityAlert "problem"

4. Just beginning

5. adding and reading new attributes from/to a declare-styleable

6. How do I know when my view will be displayed?

7. Layout with all cells the same size