From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephan Hoffmann Date: Thu, 24 Jan 2013 08:55:26 +0100 Subject: [Buildroot] Boost integration In-Reply-To: References: <201301222220.14854.yann.morin.1998@free.fr> <87libk2s6i.fsf@dell.be.48ers.dk> <87ham73n37.fsf@dell.be.48ers.dk> Message-ID: <5100E8EE.4030309@relinux.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Am 23.01.2013 18:08, schrieb Willy Lambert: > 2013/1/23 Peter Korsgaard : >>>>>>> "Willy" == Willy Lambert 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