From: ChenQi <Qi.Chen@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/4] ICU: add pkgconfig support
Date: Tue, 4 Dec 2012 10:04:05 +0800 [thread overview]
Message-ID: <50BD5A15.3020806@windriver.com> (raw)
In-Reply-To: <CAJTo0LZOOuZ7RJ+f+hXPckxRrPr9CU8c4KPT5sgSSo1rm7q=eQ@mail.gmail.com>
On 12/03/2012 07:50 PM, Burton, Ross wrote:
> On 3 December 2012 10:42,<Qi.Chen@windriver.com> wrote:
>> +ICU-3.6 has no pkgconfig, so I add it here.
>> +But ICU has had pkgconfig support since 4.6.
> Is there a reason we can't just bump oe-core to 4.6?
>
> Ross
>
I'm not sure. Maybe we bump ICU to the latest version later. (If nobody
does it, I'll find time to do it, and test it.)
The reason I add pkgconfig to ICU-3.6 is that I think it's better to do
one thing at a time.
Thanks,
Chen Qi
next prev parent reply other threads:[~2012-12-04 2:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 10:42 [PATCH 0/4] [V2] Add pkgconfig support to four packages Qi.Chen
2012-12-03 10:42 ` [PATCH 1/4] libksba: add pkgconfig support Qi.Chen
2012-12-03 10:42 ` [PATCH 2/4] ICU: " Qi.Chen
2012-12-03 11:50 ` Burton, Ross
2012-12-04 2:04 ` ChenQi [this message]
2012-12-10 16:48 ` Saul Wold
2012-12-10 21:44 ` Saul Wold
2012-12-11 1:07 ` Andreas Müller
2012-12-11 1:59 ` Saul Wold
2012-12-12 8:48 ` ChenQi
2012-12-12 8:58 ` ChenQi
2012-12-11 2:05 ` ChenQi
2012-12-03 10:42 ` [PATCH 3/4] pth: " Qi.Chen
2012-12-03 10:42 ` [PATCH 4/4] libassuan: " Qi.Chen
2012-12-04 8:51 ` [PATCH 0/4] [V3] Add pkgconfig support to four packages ChenQi
-- strict thread matches above, loose matches on Subject: below --
2012-11-26 9:36 [PATCH 0/4] " Qi.Chen
2012-11-26 9:36 ` [PATCH 2/4] icu: add pkgconfig support Qi.Chen
2012-11-26 10:56 ` Burton, Ross
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=50BD5A15.3020806@windriver.com \
--to=qi.chen@windriver.com \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.