From: GNUtoo <GNUtoo@no-log.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Boost version
Date: Tue, 30 Mar 2010 22:57:54 +0200 [thread overview]
Message-ID: <1269982674.2390.3.camel@gnutoo-desktop> (raw)
In-Reply-To: <4BB1EBEC.8050109@balister.org>
On Tue, 2010-03-30 at 08:17 -0400, Philip Balister wrote:
> I'd like to remove the DEFAULT_PREFERENCE = "-1" from the boost recipes
> so we are using the latest boost.
>
> Currently, I am checking the packages that use boost I care about, such
> as gnuradio.
>
> Does anyone else care what version of boost is the default?
I care,I prefer the last ones (1.4x) for wesnoth 1.6x
> Also, the boost-1.41 recipe is based of the cmake branch of boost. How
> well maintained is this? It has been two months since boost-1.42 was
> released and there is not corresponding cmake version.
Seem not very maintained...
Maybe look at http://gitorious.org/boost/cmake
it's their git repo.
(SRC_URI->download page->readme)
Denis
prev parent reply other threads:[~2010-03-30 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 12:17 Boost version Philip Balister
2010-03-30 20:57 ` GNUtoo [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=1269982674.2390.3.camel@gnutoo-desktop \
--to=gnutoo@no-log.org \
--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