|
@@ -294,12 +294,23 @@ HOST_ASTERISK_CONF_OPTS = \
|
|
|
--without-curses \
|
|
|
--with-ncurses=$(HOST_DIR)/usr
|
|
|
|
|
|
-# Even though menuselect is an autotools package, it is *not* installed,
|
|
|
-# as asterisk does expect it to be in a sub-directory of its source tree,
|
|
|
-# which do by copying the full menuselect build tree as a pre-configure
|
|
|
-# hook in the target variant.
|
|
|
+# Not an automake package, so does not inherit LDFLAGS et al. from
|
|
|
+# the configure run.
|
|
|
+HOST_ASTERISK_MAKE_ENV = $(HOST_CONFIGURE_OPTS)
|
|
|
+
|
|
|
+# Even though menuselect is an autotools package, it is not an automake
|
|
|
+# package and does not have an 'install' rule, as asterisk does expect
|
|
|
+# it to be in a sub-directory of its source tree. We do so by copying
|
|
|
+# the full menuselect build tree as a pre-configure hook in the target
|
|
|
+# variant.
|
|
|
+# However, the sanity checks on host packages are not run on menuselect.
|
|
|
+# But we still want to catch that menuselect has the proper rpath set,
|
|
|
+# for example, as it uses host libraries that we do build, like
|
|
|
+# host-libxml2.
|
|
|
+# So we do manually install the menuselect tool.
|
|
|
define HOST_ASTERISK_INSTALL_CMDS
|
|
|
- @:
|
|
|
+ $(INSTALL) -D -m 0755 $(@D)/menuselect/menuselect \
|
|
|
+ $(HOST_DIR)/bin/asterisk-menuselect
|
|
|
endef
|
|
|
|
|
|
$(eval $(host-autotools-package))
|