All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] Boost integration
Date: Thu, 24 Jan 2013 11:19:16 +0100	[thread overview]
Message-ID: <51010AA4.7070600@relinux.de> (raw)
In-Reply-To: <CAKvQZ_3wapLWiTp5NPQqGak911+Fgh0VX=WRo54FqFWpLAfkww@mail.gmail.com>

Am 24.01.2013 10:46, schrieb Willy Lambert:
> 2013/1/24 Stephan Hoffmann <sho@relinux.de>:
>> Am 24.01.2013 10:03, schrieb Willy Lambert:
>>> 2013/1/24 Stephan Hoffmann <sho@relinux.de>:
>>>> Am 23.01.2013 18:08, schrieb Willy Lambert:
>>>>> 2013/1/23 Peter Korsgaard <jacmet@uclibc.org>:
>>>>>>>>>>> "Willy" == Willy Lambert <lambert.willy@gmail.com> writes:
>>>> snip
>>>>>>>>>>>  Willy> I can propose you a patch to be abble to select different version a
>>>>>>>>>>>  Willy> boost in config menus. But I'm not sure that the current mk can handle
>>>>>>>>>>>  Willy> other versions.
>>>>>>>>>>>
>>>>>>>>>>> We normally don't support multiple versions of a package (except for a
>>>>>>>>>>> few minor exceptions) as that very soon becomes a support headache. Why
>>>>>>>>>>> would you want more than 1 version?
>>>>> Because I need boost for another framework, that is not supporting
>>>>> latest boost versions for now. And mainlining lastest boost support
>>>>> there is not an option (it is at best a parrallel work to do on my
>>>>> side, but I can't be on all fires ^^). And even if it compiles, I
>>>>> don't want to play with versionning incompatibilities beetwen boost
>>>>> and my framework. I need the 1.42.0 version.
>>>> Hi,
>>>>
>>>> isn't this a perfect use case for the source override feature?
>>>>
>>>> Regards
>>> I'm sorry but I don't understand what you mean but "source override
>>> feature", could you explain this ?
>> Have a look here: http://free-electrons.com/blog/buildroot-2011-11/
>>
>> I am afraid it might not be in the documentation yet.
>>
>> Stephan
> Thanks for pointing. But source override will only work if the .mk
> file is able to compile this version, right ?
Yes, that might be true.
>
> I confirmed it is not documented, or it is only suggested in a way
> that you can't guess what it is unless you already know it ^^. It's a
> pity since your blog was very clear about that, there is mainly copy
> pasting to do.
In fact that isn't my blog but Thomas', nor did I contribute any part of
this functionality. I am just using the override feature for my
application and for the kernel source.
> From my testing yesterday :
> 1.52.0 is the only version that compiles.
> 1.51.0 has a packaging problem from boost (when extracted it is inside
> a boost_1.51.0 dir intead of being flat in the BR dir)
> 1.48 to 1.50 compiles if you suppress the "context" flag
> 1.47 doesn't know about the postfix issue
> 1.42 doesn't build because "b2" doesn't exists.
>
> Is there any way to make *.mk depends on versions ? I tried to hack
> with something like
> http://stackoverflow.com/questions/5188267/checking-the-gcc-version-in-a-makefile
> without success.
I don't have an idea on this, sorry.

Regards

Stephan
>
>
>>>> Stephan
>>>>> The idea is not necessarily to maintain all boost versions, but if the
>>>>> same script can handle several one, it's a pity to just propose the
>>>>> last one.
>>>>> Said differently, I have written the part that allow to choose a
>>>>> version on the model of config files that choose kernels. If you are
>>>>> interested in them I'll send you a patch. If you think you are Ok with
>>>>> editing the boost.mk by hand I'll keep my patch locally.
>>>>>
>>>>>
>>>>>>  Willy> I personnaly put Boost in Packages->Librairies->Boost. It is currently
>>>>>>  Willy> in a "Other" menu.Don't you think it would be a better place ?
>>>>>>
>>>>>> What would Libraries->Boost contain? Just the single boost package?
>>>>> yes, but boost is a family of librairies. But anyway I don't really
>>>>> care about that.
>>>>>
>>>>>> --
>>>>>> Bye, Peter Korsgaard
>>>>> _______________________________________________
>>>>> buildroot mailing list
>>>>> buildroot at busybox.net
>>>>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>> --
>> reLinux     -    Stephan Hoffmann
>> Am Schmidtgrund 124    50765 K?ln
>> Tel. +49.221.95595-19    Fax: -64
>> www.reLinux.de     sho at reLinux.de
>>


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

      reply	other threads:[~2013-01-24 10:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 21:09 [Buildroot] Boost integration Willy Lambert
2013-01-22 21:20 ` Yann E. MORIN
2013-01-23  0:14   ` Willy Lambert
2013-01-23  1:15     ` Willy Lambert
2013-01-23  8:56       ` Peter Korsgaard
2013-01-23  9:06         ` Willy Lambert
2013-01-23  9:41           ` [Buildroot] Mono Project Berns
2013-01-23 16:01           ` [Buildroot] Boost integration Peter Korsgaard
2013-01-23 17:08             ` Willy Lambert
2013-01-24  7:55               ` Stephan Hoffmann
2013-01-24  9:03                 ` Willy Lambert
2013-01-24  9:18                   ` Stephan Hoffmann
2013-01-24  9:46                     ` Willy Lambert
2013-01-24 10:19                       ` Stephan Hoffmann [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=51010AA4.7070600@relinux.de \
    --to=sho@relinux.de \
    --cc=buildroot@busybox.net \
    /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.