1*4882a593Smuzhiyun################################################################################ 2*4882a593Smuzhiyun# 3*4882a593Smuzhiyun# skeleton 4*4882a593Smuzhiyun# 5*4882a593Smuzhiyun################################################################################ 6*4882a593Smuzhiyun 7*4882a593Smuzhiyun# The skeleton can't depend on the toolchain, since all packages depends on the 8*4882a593Smuzhiyun# skeleton and the toolchain is a target package, as is skeleton. 9*4882a593Smuzhiyun# Hence, skeleton would depends on the toolchain and the toolchain would depend 10*4882a593Smuzhiyun# on skeleton. 11*4882a593SmuzhiyunSKELETON_ADD_TOOLCHAIN_DEPENDENCY = NO 12*4882a593SmuzhiyunSKELETON_ADD_SKELETON_DEPENDENCY = NO 13*4882a593Smuzhiyun 14*4882a593Smuzhiyun# We create a compatibility symlink in case a post-build script still 15*4882a593Smuzhiyun# uses $(HOST_DIR)/usr 16*4882a593Smuzhiyundefine HOST_SKELETON_INSTALL_CMDS 17*4882a593Smuzhiyun $(Q)ln -snf . $(HOST_DIR)/usr 18*4882a593Smuzhiyun $(Q)mkdir -p $(HOST_DIR)/lib 19*4882a593Smuzhiyun $(Q)mkdir -p $(HOST_DIR)/include 20*4882a593Smuzhiyun $(Q)case $(HOSTARCH) in \ 21*4882a593Smuzhiyun (*64) ln -snf lib $(HOST_DIR)/lib64;; \ 22*4882a593Smuzhiyun (*) ln -snf lib $(HOST_DIR)/lib32;; \ 23*4882a593Smuzhiyun esac 24*4882a593Smuzhiyunendef 25*4882a593Smuzhiyun 26*4882a593Smuzhiyun$(eval $(virtual-package)) 27*4882a593Smuzhiyun$(eval $(host-generic-package)) 28