* [Buildroot] Boost integration @ 2013-01-22 21:09 Willy Lambert 2013-01-22 21:20 ` Yann E. MORIN 0 siblings, 1 reply; 14+ messages in thread From: Willy Lambert @ 2013-01-22 21:09 UTC (permalink / raw) To: buildroot Hi, I created a package for Boost on my personnal repo. Are you interested in getting this mainlined ? One of the most challenging part of it is the version management as Boost has a quite high frequency delivery rate, has many independant librairies (so it requires an important Config.in job) and that they changed their buildsystem recently (1.45.0). I have already a package working for 1.40.0 to 1.44.0 that I get from someone with some librairies. ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 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 0 siblings, 1 reply; 14+ messages in thread From: Yann E. MORIN @ 2013-01-22 21:20 UTC (permalink / raw) To: buildroot Willy, All, On Tuesday 22 January 2013 Willy Lambert wrote: > I created a package for Boost on my personnal repo. Are you interested > in getting this mainlined ? There's already a boost package in mainline Buildroot: http://git.buildroot.net/buildroot/tree/package/boost Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 2013-01-22 21:20 ` Yann E. MORIN @ 2013-01-23 0:14 ` Willy Lambert 2013-01-23 1:15 ` Willy Lambert 0 siblings, 1 reply; 14+ messages in thread From: Willy Lambert @ 2013-01-23 0:14 UTC (permalink / raw) To: buildroot 2013/1/22 Yann E. MORIN <yann.morin.1998@free.fr>: > Willy, All, > > On Tuesday 22 January 2013 Willy Lambert wrote: >> I created a package for Boost on my personnal repo. Are you interested >> in getting this mainlined ? > > There's already a boost package in mainline Buildroot: > http://git.buildroot.net/buildroot/tree/package/boost > > Regards, > Yann E. MORIN. > > -- wouat ? how the hell don't I have it ... > .-----------------.--------------------.------------------.--------------------. > | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | > | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | > | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | > | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | > '------------------------------^-------^------------------^--------------------' > ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 2013-01-23 0:14 ` Willy Lambert @ 2013-01-23 1:15 ` Willy Lambert 2013-01-23 8:56 ` Peter Korsgaard 0 siblings, 1 reply; 14+ messages in thread From: Willy Lambert @ 2013-01-23 1:15 UTC (permalink / raw) To: buildroot 2013/1/23 Willy Lambert <lambert.willy@gmail.com>: > 2013/1/22 Yann E. MORIN <yann.morin.1998@free.fr>: >> Willy, All, >> >> On Tuesday 22 January 2013 Willy Lambert wrote: >>> I created a package for Boost on my personnal repo. Are you interested >>> in getting this mainlined ? >> >> There's already a boost package in mainline Buildroot: >> http://git.buildroot.net/buildroot/tree/package/boost >> >> Regards, >> Yann E. MORIN. >> >> -- > > wouat ? > > how the hell don't I have it ... > I see that you put the sources tarball on : http://sources.buildroot.net/ and many other are taken from here. Is it a good practice to put all there to keep the availibility of all links, or is it just because no external links exist ? > >> .-----------------.--------------------.------------------.--------------------. >> | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | >> | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | >> | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | >> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | >> '------------------------------^-------^------------------^--------------------' >> ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 2013-01-23 1:15 ` Willy Lambert @ 2013-01-23 8:56 ` Peter Korsgaard 2013-01-23 9:06 ` Willy Lambert 0 siblings, 1 reply; 14+ messages in thread From: Peter Korsgaard @ 2013-01-23 8:56 UTC (permalink / raw) To: buildroot >>>>> "Willy" == Willy Lambert <lambert.willy@gmail.com> writes: Hi, Willy> I see that you put the sources tarball on : Willy> http://sources.buildroot.net/ Willy> and many other are taken from here. Willy> Is it a good practice to put all there to keep the availibility Willy> of all links, or is it just because no external links exist ? It's just a backup in case upstream is down/disappears. -- Bye, Peter Korsgaard ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 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 0 siblings, 2 replies; 14+ messages in thread From: Willy Lambert @ 2013-01-23 9:06 UTC (permalink / raw) To: buildroot 2013/1/23 Peter Korsgaard <jacmet@uclibc.org>: >>>>>> "Willy" == Willy Lambert <lambert.willy@gmail.com> writes: > > Hi, > > Willy> I see that you put the sources tarball on : > Willy> http://sources.buildroot.net/ > Willy> and many other are taken from here. > > Willy> Is it a good practice to put all there to keep the availibility > Willy> of all links, or is it just because no external links exist ? > > It's just a backup in case upstream is down/disappears. > > -- > Bye, Peter Korsgaard Ok, then the current link to boost sourceforge seems broken, does anyone else has the same problem ? Maybe : BOOST_SITE = http://sourceforge.net/projects/boost/files/boost/$(BOOST_VERSION) would be a working solution, butI found it by tries and fails so it is maybe not the best link. I can propose you a patch to be abble to select different version a boost in config menus. But I'm not sure that the current mk can handle other versions. I personnaly put Boost in Packages->Librairies->Boost. It is currently in a "Other" menu.Don't you think it would be a better place ? ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Mono Project 2013-01-23 9:06 ` Willy Lambert @ 2013-01-23 9:41 ` Berns 2013-01-23 16:01 ` [Buildroot] Boost integration Peter Korsgaard 1 sibling, 0 replies; 14+ messages in thread From: Berns @ 2013-01-23 9:41 UTC (permalink / raw) To: buildroot Hi, has anyone done some work/ tests with Mono and Buildroot in the past or is currently working on it ? I want to do some tests with a Beaglebone board. Regards Rainer ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 2013-01-23 9:06 ` Willy Lambert 2013-01-23 9:41 ` [Buildroot] Mono Project Berns @ 2013-01-23 16:01 ` Peter Korsgaard 2013-01-23 17:08 ` Willy Lambert 1 sibling, 1 reply; 14+ messages in thread From: Peter Korsgaard @ 2013-01-23 16:01 UTC (permalink / raw) To: buildroot >>>>> "Willy" == Willy Lambert <lambert.willy@gmail.com> writes: Hi, >> It's just a backup in case upstream is down/disappears. Willy> Ok, then the current link to boost sourceforge seems broken, does Willy> anyone else has the same problem ? Why? It works here: make boost-source >>> boost 1.52.0 Downloading --2013-01-23 16:59:21-- http://downloads.sourceforge.net/project/boost/boost/1.52.0/boost_1_52_0.tar.bz2 Resolving downloads.sourceforge.net (downloads.sourceforge.net)... 216.34.181.59 Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|216.34.181.59|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://switch.dl.sourceforge.net/project/boost/boost/1.52.0/boost_1_52_0.tar.bz2 [following] --2013-01-23 16:59:21-- http://switch.dl.sourceforge.net/project/boost/boost/1.52.0/boost_1_52_0.tar.bz2 Resolving switch.dl.sourceforge.net (switch.dl.sourceforge.net)... 130.59.138.21, 2001:620:0:1b::21 Connecting to switch.dl.sourceforge.net (switch.dl.sourceforge.net)|130.59.138.21|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 54421709 (52M) [application/x-bzip2] Saving to: `/var/lib/downloads/boost_1_52_0.tar.bz2.tmp' Doesn't that work for you? 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? 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? -- Bye, Peter Korsgaard ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 2013-01-23 16:01 ` [Buildroot] Boost integration Peter Korsgaard @ 2013-01-23 17:08 ` Willy Lambert 2013-01-24 7:55 ` Stephan Hoffmann 0 siblings, 1 reply; 14+ messages in thread From: Willy Lambert @ 2013-01-23 17:08 UTC (permalink / raw) To: buildroot 2013/1/23 Peter Korsgaard <jacmet@uclibc.org>: >>>>>> "Willy" == Willy Lambert <lambert.willy@gmail.com> writes: > > Hi, > > >> It's just a backup in case upstream is down/disappears. > > Willy> Ok, then the current link to boost sourceforge seems broken, does > Willy> anyone else has the same problem ? > > Why? It works here: > > make boost-source >>>> boost 1.52.0 Downloading > --2013-01-23 16:59:21-- http://downloads.sourceforge.net/project/boost/boost/1.52.0/boost_1_52_0.tar.bz2 > Resolving downloads.sourceforge.net (downloads.sourceforge.net)... 216.34.181.59 > Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|216.34.181.59|:80... connected. > HTTP request sent, awaiting response... 302 Found > Location: http://switch.dl.sourceforge.net/project/boost/boost/1.52.0/boost_1_52_0.tar.bz2 [following] > --2013-01-23 16:59:21-- http://switch.dl.sourceforge.net/project/boost/boost/1.52.0/boost_1_52_0.tar.bz2 > Resolving switch.dl.sourceforge.net (switch.dl.sourceforge.net)... 130.59.138.21, 2001:620:0:1b::21 > Connecting to switch.dl.sourceforge.net (switch.dl.sourceforge.net)|130.59.138.21|:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: 54421709 (52M) [application/x-bzip2] > Saving to: `/var/lib/downloads/boost_1_52_0.tar.bz2.tmp' > > Doesn't that work for you? It is working here, don't know what happened yesterday at home. > > 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. 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 2013-01-23 17:08 ` Willy Lambert @ 2013-01-24 7:55 ` Stephan Hoffmann 2013-01-24 9:03 ` Willy Lambert 0 siblings, 1 reply; 14+ messages in thread From: Stephan Hoffmann @ 2013-01-24 7:55 UTC (permalink / raw) To: buildroot 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 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 2013-01-24 7:55 ` Stephan Hoffmann @ 2013-01-24 9:03 ` Willy Lambert 2013-01-24 9:18 ` Stephan Hoffmann 0 siblings, 1 reply; 14+ messages in thread From: Willy Lambert @ 2013-01-24 9:03 UTC (permalink / raw) To: buildroot 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 ? > > 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 > ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 2013-01-24 9:03 ` Willy Lambert @ 2013-01-24 9:18 ` Stephan Hoffmann 2013-01-24 9:46 ` Willy Lambert 0 siblings, 1 reply; 14+ messages in thread From: Stephan Hoffmann @ 2013-01-24 9:18 UTC (permalink / raw) To: buildroot 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 > >> 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 2013-01-24 9:18 ` Stephan Hoffmann @ 2013-01-24 9:46 ` Willy Lambert 2013-01-24 10:19 ` Stephan Hoffmann 0 siblings, 1 reply; 14+ messages in thread From: Willy Lambert @ 2013-01-24 9:46 UTC (permalink / raw) To: buildroot 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 ? 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. 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. >> >>> 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 > ^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Boost integration 2013-01-24 9:46 ` Willy Lambert @ 2013-01-24 10:19 ` Stephan Hoffmann 0 siblings, 0 replies; 14+ messages in thread From: Stephan Hoffmann @ 2013-01-24 10:19 UTC (permalink / raw) To: buildroot 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2013-01-24 10:19 UTC | newest] Thread overview: 14+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox