Michael Buesch wrote: > Why do we need the following RequireCommand in enlightenment? > > $(eval $(call RequireCommand,edje_cc, \ > Command <edje_cc> not found - please install edje with edje-cc enabled \ > )) > $(eval $(call RequireCommand,eet, \ > Command <eet> not found - please install eet \ > )) > > As far as I understand, this checks for the two commands on the build host > system. Yep. > Why? Why don't we simply build the tools? Because building native host tools isn't possible in a nice way yet. > Don't we actually _do_ the build already? No, building of edje_cc is disabled in the Makefile. > I guess so, because the configure target redirects these commands to staging: > > define Build/Configure > (cd $(PKG_BUILD_DIR); NOCONFIGURE=YES ./autogen.sh ); > $(call Build/Configure/Default, > --with-edje-cc=$(STAGING_DIR_HOST)/usr/bin/edje_cc > --with-eet-eet=$(STAGING_DIR_HOST)/usr/bin/eet) > endef That just refers to the host edje_cc. $(STAGING_DIR_HOST)/usr/bin/edje_cc is a symlink, same with eet. > mirko
-- This email address is used for mailinglist purposes only. Non-mailinglist emails will be dropped automatically. If you want to get in contact with me personally, please mail to: mirko.vogt <at> nanl <dot> de _______________________________________________ openwrt-devel mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
