From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>,
Koen Kooi <koen@openembedded.org>
Subject: Re: [PATCH] libvpx: disabled explicitly the generation of docs
Date: Fri, 4 Jun 2010 15:08:55 -0700 [thread overview]
Message-ID: <20100604220855.GA27712@gmail.com> (raw)
In-Reply-To: <1275673186-16695-1-git-send-email-enrico.scholz@sigma-chemnitz.de>
On (04/06/10 19:39), Enrico Scholz wrote:
> When buildsystem has 'doxygen' and 'php' the documentation will be
> created and the path in do_install (vpx-vp8-nopost-nodocs) won't be
> found anymore:
where do they get put when doxygen and php are found. You may also
put doxygen-native and php-native in DEPENDS and generate the documentation
always but that may be overkill if we already have documentation prebuilt
which can be installed. is that the case?
>
> | make[2]: Leaving directory `.../libvpx-0.9.0-r2/libvpx-0.9.0'
> | + cp -r '.../libvpx-0.9.0/vpx-vp8-nopost-nodocs*0.9.0/*' .../image/usr/
> | cp: cannot stat `.../libvpx-0.9.0/vpx-vp8-nopost-nodocs*0.9.0/*': No such file or directory
> | ERROR: Function do_install failed NOTE: package libvpx-0.9.0-r2: task do_install: Failed
>
> This patch makes the build more deterministic.
>
> Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
> Cc: Koen Kooi <koen@openembedded.org>
> ---
> recipes/webm/libvpx_0.9.0.bb | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/recipes/webm/libvpx_0.9.0.bb b/recipes/webm/libvpx_0.9.0.bb
> index a59d94d..b55604b 100644
> --- a/recipes/webm/libvpx_0.9.0.bb
> +++ b/recipes/webm/libvpx_0.9.0.bb
> @@ -1,7 +1,7 @@
> DESCRIPTION = "vpx Multi-Format Codec SDK"
> LICENSE = "VP8"
>
> -PR = "r2"
> +PR = "r3"
>
> SRC_URI = "http://webm.googlecode.com/files/libvpx-${PV}.tar.bz2"
>
> @@ -20,6 +20,7 @@ VPXTARGET ?= "generic-gnu"
>
> CONFIGUREOPTS = " \
> --target=${VPXTARGET} \
> + --disable-install_docs \
Does it disable the doc generation completely ?
> --enable-vp8 \
> --enable-libs \
> "
> --
> 1.7.0.1
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-06-04 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 17:39 [PATCH] libvpx: disabled explicitly the generation of docs Enrico Scholz
2010-06-04 22:08 ` Khem Raj [this message]
2010-06-04 23:34 ` Enrico Scholz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100604220855.GA27712@gmail.com \
--to=raj.khem@gmail.com \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=koen@openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.