解决openwrt ipk missing dependencies libpthread librt

新版本的trunk有在ipk打包的过程中的bug，他不能自动识别SDK中已经变异的动态链接库，比如libpthread，libboost这些。

解决方案是修改与pakage里同级的makefile的内容：

可以修改如下：

主要是添加DEPENDS与拷贝动态链接库到安装目录。找了很久，很多国外的论坛才，找到的思路。

##############################################
# OpenWrt Makefile for Scada_Em program
#
#
# Most of the variables used here are defined in
# the include directives below. We just need to
# specify a basic description of the package,
# where to build our program, where to find
# the source files, and where to install the
# compiled program on the router.
#
# Be very careful of spacing in this file.
# Indents should be tabs, not spaces, and
# there should be no trailing whitespace in
# lines that are not commented.
#
##############################################

include $(TOPDIR)/rules.mk

# Name and release number of this package
PKG_NAME:=Scada_Em
PKG_RELEASE:=1


# This specifies the directory where we're going to build the program. 
# The root build directory, $(BUILD_DIR), is by default the build_mipsel
# directory in your OpenWrt SDK directory
PKG_BUILD_DIR := $(BUILD_DIR)/$(PKG_NAME)


include $(INCLUDE_DIR)/package.mk

# Specify package information for this program.
# The variables defined here should be self explanatory.
# If you are running Kamikaze, delete the DESCRIPTION
# variable below and uncomment the Kamikaze define
# directive for the description below
define Package/Scada_Em
	SECTION:=utils
	CATEGORY:=Utilities
	TITLE:=Scada_Em -- prints a snarky message
	DEPENDS:=+libpthread +librt
endef

# Uncomment portion below for Kamikaze and delete DESCRIPTION variable above
define Package/Scada_Em/description
	If you can't figure out what this program does, you're probably
	brain-dead and need immediate medical attention.
endef



# Specify what needs to be done to prepare for building the package.
# In our case, we need to copy the source files to the build directory.
# This is NOT the default.  The default uses the PKG_SOURCE_URL and the
# PKG_SOURCE which is not defined here to download the source from the web.
# In order to just build a simple program that we have just written, it is
# much easier to do it this way.
define Build/Prepare
	mkdir -p $(PKG_BUILD_DIR)
	$(CP) ./src/* $(PKG_BUILD_DIR)/
endef


# We do not need to define Build/Configure or Build/Compile directives
# The defaults are appropriate for compiling a simple program such as this one


# Specify where and how to install the program. Since we only have one file,
# the Scada_Em executable, install it by copying it to the /bin directory on
# the router. The $(1) variable represents the root directory on the router running
# OpenWrt. The $(INSTALL_DIR) variable contains a command to prepare the install
# directory if it does not already exist.  Likewise $(INSTALL_BIN) contains the
# command to copy the binary file from its current location (in our case the build
# directory) to the install directory.
#define Package/Scada_Em/install
#	$(INSTALL_DIR) $(1)/bin
#	$(INSTALL_BIN) $(PKG_BUILD_DIR)/Scada_Em $(1)/bin/
#
#	$(INSTALL_DIR) $(1)/usr/lib
#endef

define Package/Scada_Em/install
	$(INSTALL_DIR) $(1)/bin
	$(CP) /home/zchx/3rdLib_mipsel/lib{boost_system,boost_thread,stdc++}.so.* $(1)/bin/
	$(INSTALL_BIN) $(PKG_BUILD_DIR)/Scada_Em $(1)/bin/
endef

# This line executes the necessary commands to compile our program.
# The above define directives specify all the information needed, but this
# line calls BuildPackage which in turn actually uses this information to
# build a package.
$(eval $(call BuildPackage,Scada_Em))

如果你遇到类似的问题，可以联系我。