Phil Sutter dixit:
>Anyway, I consider this as rather a bad solution,
Especially since the template itself contains some "dependency".
But either we do that or we cannot build packages that aren't
selected in "menuconfig".
>What about some make function like:
We already have
| ifeq ($(FWRT_PACKAGE_$(1)),y)
in the template, but this is seemingly not used at the moment.
This did what could fix this "mess", and I know how to reactivate
it, but then, nobody could build packages manually without going
through a menuconfig -> split cycle any more.
Now I could reactivate that, and we change every Makefile:
-$(eval $(call PKG_template,MKSH,mksh,${PKG_VERSION}-${PKG_RELEASE},${ARCH}))
+$(eval $(call PKG_template,y,mksh,${PKG_VERSION}-${PKG_RELEASE},${ARCH}))
and set FWRT_PACKAGE_y=y, and in your asterisk case, you would have
| $(eval $(call PKG_template,y,asterisk,$(PKG_VERSION)-$(PKG_RELEASE),$(ARCH)))
| $(eval $(call
PKG_template,ASTERISK_PGSQL,asterisk-pgsql,$(PKG_VERSION)-$(PKG_RELEASE),
| $(eval $(call
PKG_template,ASTERISK_SQLITE,asterisk-sqlite,$(PKG_VERSION)-$(PKG_RELEASE
| […]
i.e. the 'y' only for the first package.
An alternative solution:
- ifeq ($(FWRT_PACKAGE_$(1)),y)
+ ifneq (${FWRT_PACKAGE_$(1)}${DEVELOPER},)
(the top-level stuff sets DEVELOPER=1 when doing make package=foo bar).
Or we could "just" go back to the menuconfig stuff. But this requires
discussion (I already started to point this out in the private mail
yesterday).
//mirabile
--
"Using Lynx is like wearing a really good pair of shades: cuts out
the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
-- Henry Nelson, March 1999
_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers
