All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: poky@yoctoproject.org
Subject: Re: [PATCH] bitbake docs: use dblatex to build the pdf bitbake manual
Date: Mon, 14 Mar 2011 17:52:28 +0000	[thread overview]
Message-ID: <1300125148.2802.27.camel@scimitar> (raw)
In-Reply-To: <edad97936654f13dbbef0651f508615dc4c89e65.1299705776.git.dvhart@linux.intel.com>

On Wed, 2011-03-09 at 13:32 -0800, Darren Hart wrote:
> From: Darren Hart <dvhart@linux.intel.com>
> 
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>   Branch: dvhart/doc
>   Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/doc
> 
> Thanks,
>     Darren Hart <dvhart@linux.intel.com>
> 
> Darren Hart (1):
>   bitbake docs: use dblatex to build the pdf bitbake manual
> 
>  bitbake/doc/manual/Makefile |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> Fix [BUGID #593]
> 
> The current manual build fails for printing formats which use latex as an
> intermediate format. This bug has been reported in multiple locations and I
> haven't found a solution posted to any of them.
> 
> Using --with-dblatex uses dblatex to make the conversion and successfully
> generates the pdf. It adds a dependency on dblatex and its dependencies.
> 
> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
> CC: Joshua Lock <josh@linux.intel.com>

With this patch and dblatex installed I am able to build the BitBake
manual.

Signed-off-by: Joshua Lock <josh@linux.intel.com>

Cheers,
Joshua
-- 
Joshua Lock
        Yocto Build System Monkey
        Intel Open Source Technology Centre



      reply	other threads:[~2011-03-14 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 21:32 [PATCH] bitbake docs: use dblatex to build the pdf bitbake manual Darren Hart
2011-03-14 17:52 ` Joshua Lock [this message]

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=1300125148.2802.27.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=poky@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.