From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/7] apr-util: Upgrade to 1.3.12
Date: Tue, 02 Aug 2011 15:53:09 +0800 [thread overview]
Message-ID: <4E37ACE5.6000300@intel.com> (raw)
In-Reply-To: <2074233.Hg07R4aRha@perseus>
Khem Raj wrote:
>
> On Thursday, July 28, 2011 09:03:06 PM edwin.zhai@intel.com wrote:
> >
> >
> > +FILES_${PN}-dev += "${libdir}/aprutil.exp"
> > +FILES_${PN} += "${libdir}/apr-util-1/apr_dbm_gdbm-1.so"
> > +FILES_${PN}-dbg += "${libdir}/apr-util-1/*
> ${libdir}/apr-util-1/.debug/*"
>
> do you really want ${libdir}/apr-util-1/* wildcard to go into a dbg
> package
> here ?
>
2nd thought make them into dev package like following:
+FILES_${PN} += "${libdir}/apr-util-1/apr_dbm_gdbm-1.so"
+FILES_${PN}-dev += "${libdir}/aprutil.exp
${libdir}/apr-util-1/apr_dbm_gdbm.*"
+FILES_${PN}-dbg += "${libdir}/apr-util-1/.debug/*"
> > +
> --
> Khem Raj
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-08-02 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 13:03 [PATCH 0/7] packages upgrade, Edwin, July 28, 2011 edwin.zhai
2011-07-28 13:03 ` [PATCH 1/7] lighttpd: Upgrade to 1.4.29 edwin.zhai
2011-07-28 13:03 ` [PATCH 2/7] libsoup-2.4: Upgrade to 2.34.2 edwin.zhai
2011-07-28 13:03 ` [PATCH 3/7] apr: Upgrade to 1.4.5 edwin.zhai
2011-07-30 18:47 ` Khem Raj
2011-07-28 13:03 ` [PATCH 4/7] apr-util: Upgrade to 1.3.12 edwin.zhai
2011-07-30 18:48 ` Khem Raj
2011-08-02 7:53 ` Zhai, Edwin [this message]
2011-07-28 13:03 ` [PATCH 5/7] libassuan: Upgrade to 2.0.2 edwin.zhai
2011-07-28 13:03 ` [PATCH 6/7] gpgme: Upgrade to 1.3.1 edwin.zhai
2011-07-28 13:03 ` [PATCH 7/7] parted: Upgrade to 3.0 edwin.zhai
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=4E37ACE5.6000300@intel.com \
--to=edwin.zhai@intel.com \
--cc=openembedded-core@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