On 26 February 2016 at 01:45, Hongxu Jia <hongxu....@windriver.com> wrote:
> +do_unpack[postfuncs] += "unpack_waf"
> +do_unpack[vardeps] += "unpack_waf"
> +unpack_waf() {
> + # Just self extract tarball embedded in waf, do not care help
> message.
> + # Do not generate bytecode, becuase we need to patch python file
> later
> + PYTHONDONTWRITEBYTECODE=True ./waf --help >/dev/null
> +}
>
Presumably this isn't pycairo-specific but impacts every recipe using waf?
> do_configure() {
> - BUILD_SYS=${BUILD_SYS} HOST_SYS=${HOST_SYS} ./waf configure
> --prefix=${D}${prefix} --libdir=${D}${libdir}
> + BUILD_SYS=${BUILD_SYS} HOST_SYS=${HOST_SYS} ./waf configure
> --prefix=${prefix} --libdir=${libdir}
> }
>
Looks like this recipe needs to use the waf class for a start.
Ross
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
