Use ln(1) rather than cp(1) to set up host /system for testing.

The trouble with cp is that if you're running a command directly (because
you're using gdb, say), you need to make sure you've copied the linker
and shell again if you've done a rebuild that caused a change there.

Change-Id: I312da30c0f92b515967e854e0faba272c961ecc7
This commit is contained in:
Elliott Hughes 2014-10-08 14:56:27 -07:00
parent 1364101067
commit 3ea4d56ed4

View File

@ -401,8 +401,8 @@ bionic-unit-tests-run-on-host: bionic-unit-tests $(TARGET_OUT_EXECUTABLES)/$(LIN
sudo mkdir -p -m 0777 /system/bin; \
fi
mkdir -p $(TARGET_OUT_DATA)/local/tmp
cp $(TARGET_OUT_EXECUTABLES)/$(LINKER) /system/bin
cp $(TARGET_OUT_EXECUTABLES)/sh /system/bin
ln -fs `realpath $(TARGET_OUT_EXECUTABLES)/$(LINKER)` /system/bin
ln -fs `realpath $(TARGET_OUT_EXECUTABLES)/sh` /system/bin
ANDROID_DATA=$(TARGET_OUT_DATA) \
ANDROID_ROOT=$(TARGET_OUT) \
LD_LIBRARY_PATH=$(TARGET_OUT_SHARED_LIBRARIES) \
@ -417,8 +417,8 @@ bionic-unit-tests-run-on-host32: bionic-unit-tests_32 $(TARGET_OUT_EXECUTABLES)/
sudo mkdir -p -m 0777 /system/bin; \
fi
mkdir -p $(TARGET_OUT_DATA)/local/tmp
cp $(TARGET_OUT_EXECUTABLES)/linker /system/bin
cp $(TARGET_OUT_EXECUTABLES)/sh /system/bin
ln -fs `realpath $(TARGET_OUT_EXECUTABLES)/linker` /system/bin
ln -fs `realpath $(TARGET_OUT_EXECUTABLES)/sh` /system/bin
ANDROID_DATA=$(TARGET_OUT_DATA) \
ANDROID_ROOT=$(TARGET_OUT) \
LD_LIBRARY_PATH=$(2ND_TARGET_OUT_SHARED_LIBRARIES) \