From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 3/3] mupdf-0.6: new recipe
Date: Sun, 18 Jul 2010 12:40:00 +0200 [thread overview]
Message-ID: <20100718104000.GE16225@jama> (raw)
In-Reply-To: <20100609133618.GC29724@gmail.com>
On Wed, Jun 09, 2010 at 06:36:18AM -0700, Khem Raj wrote:
> On (09/06/10 11:33), Dmitry Artamonow wrote:
> > +do_configure() {
> > + cp ${WORKDIR}/Makerules ${S}/Makerules
> > +
>
> Why not create a patch for Makerules instread of creating a file and then
> copying. It will help upgrades the patch will get refreshed for any changes
> but this will overwrite those changes.
This Makerules doesn't work very well for me
oe_runmake build/debug/cmapdump LD=${BUILD_CC} CC=${BUILD_CC}
oe_runmake build/debug/fontdump LD=${BUILD_CC} CC=${BUILD_CC}
needs couple of -native stuff missing in DEPENDS and then pkg-config
doesn't find ie freetype, because my host system doesn't have freetype
etc.
Any advice? (using pkg-config from armv4 staging dir returns right
freetype for non-native build, but injects the same libs to
cmapdump/fontdump which of course fails.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-07-18 10:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 7:32 [PATCH 0/3] Recipe for MuPDF Dmitry Artamonow
2010-06-09 7:33 ` [PATCH 1/3] openjpeg-1.3: new recipe Dmitry Artamonow
2010-06-09 7:33 ` [PATCH 2/3] jbig2dec-0.11: " Dmitry Artamonow
2010-06-09 13:31 ` Khem Raj
2010-06-09 19:46 ` Dmitry Artamonow
2010-06-09 7:33 ` [PATCH 3/3] mupdf-0.6: " Dmitry Artamonow
2010-06-09 13:36 ` Khem Raj
2010-06-09 19:37 ` Dmitry Artamonow
2010-07-18 10:40 ` Martin Jansa [this message]
2010-07-18 7:56 ` [PATCH 0/3] Recipe for MuPDF Martin Jansa
2010-08-02 8:52 ` Martin Jansa
-- strict thread matches above, loose matches on Subject: below --
2010-06-23 17:00 [PATCH v2 " Dmitry Artamonow
2010-06-23 17:00 ` [PATCH 3/3] mupdf-0.6: new recipe Dmitry Artamonow
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=20100718104000.GE16225@jama \
--to=martin.jansa@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox