From: Randy Witt <randy.e.witt@linux.intel.com>
To: Preeti P <itspreetip89@gmail.com>, yocto <yocto@yoctoproject.org>
Subject: Re: : About adding documentation in final SDK image
Date: Thu, 26 Mar 2015 13:11:12 -0700 [thread overview]
Message-ID: <551467E0.7010800@linux.intel.com> (raw)
In-Reply-To: <CA+jjunCbZfd-b+V_ipMtdWkkLwyN6xJJH3vhHjGmKG8p8b8doA@mail.gmail.com>
Hi Preeti,
On 03/19/2015 09:07 AM, Preeti P wrote:
> Hi all,
>
> I am working on adding the documents in to my SDK image.
> Basically, I want to have the man and info documentation for the tool-chain
> item in my SDK image.
>
> As per my understanding, the install package for every recipe gets split
> into different packages and finally shipped in to the SDK image.
>
> To add the documents in my SDK image, I tried to add the '-doc' support in
> 'PACKAGES' variable but still the documentation related files are not there
> in the final image.
>
> I even tried by adding below lines in to the do_install function in my
> recipe but my final image does not have those files:
>
> do_install {
>
> install -d ${D}${includedir}${doc}
>
> install -m 644 ${S}/doc/*.info ${D}${includedir}${doc}
>
> }
>
> Can anyone provide me inputs on how to add the documentation for packages
> in to the final SDK image?
I'm not sure whether you want them in the host sysroot or the target sysroot,
but will either TOOLCHAIN_HOST_TASK or TOOLCHAIN_TARGET_TASK do what you need?
https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-TOOLCHAIN_HOST_TASK
https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-TOOLCHAIN_TARGET_TASK
> Thanks,
> Preeti
>
next prev parent reply other threads:[~2015-03-26 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+jjunDcbN-xq8TUB_8y6+HKnhErtckaGYgU7RnhGxV0OC1Qfw@mail.gmail.com>
2015-03-19 16:07 ` : About adding documentation in final SDK image Preeti P
2015-03-26 20:11 ` Randy Witt [this message]
2015-03-27 14:39 ` Paul Eggleton
2015-03-26 15:26 ` Preeti P
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=551467E0.7010800@linux.intel.com \
--to=randy.e.witt@linux.intel.com \
--cc=itspreetip89@gmail.com \
--cc=yocto@yoctoproject.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.