Re: [android-building] Android.mk not copying to /system

2017-02-18 Thread 'Dan Willemsen' via Android Building
TARGET_ROOT_OUT_SBIN would put that executable in /root/sbin, which is the root ramdisk, not the system partition. There isn't a /system/sbin, we just put everything in /system/bin. - Dan On Sat, Feb 18, 2017 at 8:15 AM 'Ryan Philips' via Android Building < android-building@googlegroups.com>

Re: [android-building] Android.mk not copying to /system

2017-02-18 Thread Colin Cross
What command are you using to build? You generally need to ask the build system to install a module for you by adding it to PRODUCT_PACKAGES for the product you are building. If you are just testing locally, running mmma external/mytest should build and install everything defined in

[android-building] Android.mk not copying to /system

2017-02-18 Thread 'Ryan Philips' via Android Building
Hi, I am trying to build a test source. I have created an external/mytest directory and the following in Android.mk include $(CLEAR_VARS) LOCAL_SRC_FILES := testextspi.c LOCAL_MODULE:= testextspi LOCAL_MODULE_PATH := $(TARGET_ROOT_OUT_SBIN) LOCAL_UNSTRIPPED_PATH :=