2010/11/18 Bas Mevissen <ab...@basmevissen.nl>

> On Thu, 18 Nov 2010 15:18:52 +0100, Jan Willies <j...@willies.info>
> wrote:
>
> > define Build/Configure
> >
> >         cd $(PKG_BUILD_DIR)
> >         $(STAGING_DIR)/../host/bin/cmake .
> > endef
> >
>
> The host bin dir is already in the path, so you should be able to call
> cmake without defining a patch
>
> We could also define $CMAKE in rules.mk to have a better definition:
>
> Index: rules.mk
> ===================================================================
> --- rules.mk    (revision 24025)
> +++ rules.mk    (working copy)
> @@ -164,6 +164,9 @@
>  TARGET_CXX:=$(if $(CONFIG_INSTALL_LIBSTDCPP),$(TARGET_CROSS)g++,no)
>  KPATCH:=$(SCRIPT_DIR)/patch-kernel.sh
>  SED:=$(STAGING_DIR_HOST)/bin/sed -i -e
> +ifneq ($(CONFIG_CMAKE),)
> +  export CMAKE=$(STAGING_DIR_HOST)/bin/cmake
> +endif
>  CP:=cp -fpR
>  LN:=ln -sf
>

I guess that'd make sense.


> (I'm not sure where to put it in the rules.mk file)
>
> > CMake Error: The source directory
> > "/var/tmp/swjawill/openwrt-dockstar/feeds/packages/net/weechat" does
> > not appear to contain CMakeLists.txt.
>
> That is because CMAKE is ran in the wrong directory. Try something like
>
> define Build/Configure
>        (cd $(PKG_BUILD_DIR); \
>                $(CMAKE) . || exit 1 \
>        );
>        $(call Build/Configure/Default)
> endef
>

Yeah that works. Though I need to omit Build/Configure/Default, because that
invokes the autotool stuff in weechat which cmake is supposed to replace.

Unfortunately cmake picks up the host-gcc:

(cd
/var/tmp/swjawill/openwrt-dockstar/build_dir/target-arm_v5te_uClibc-0.9.30.1_eabi/weechat-0.3.3;
/var/tmp/swjawill/openwrt-dockstar/staging_dir/host/bin/cmake . || exit 1 );
-- The C compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
[...]

Am I supposed to call it with some options or something?
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to