They've finally released boost library version 1.32, as you can see in http://www.boost.org. I personally need this version because the app I'm working on uses it. I've managed to just get the 1.31 ebuild and adapt it to 1.32 with no problems. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 44446 [details] Sample ebuild for 1.32 This is an ebuild for 1.32 that worked for me. It's almost line for line a copy of the 1.31 ebuild, but I'm too lazy to use patch. ;-)
Created attachment 44764 [details, diff] Patch for Sample ebuild for boost-1.32 Some files for documentation had changed in version 1.32. This patch will install missing images. Jan
Created attachment 44772 [details, diff] New Patch for Sample ebuild for boost-1.32.0 - Images from Documentation in 1.32 changed - license changed from "freedist" to "Boost-1.0" - $Header: $ added
Can we get this to use the Boost build/make/install stuff instead of us hacking on our own find-xargs cruft?
This is the reference documentation that we should consult: http://boost.org/more/getting_started.html There are two things that should/need to be set with the bjam build: PYTHON_ROOT : defaults to /usr/local, gentoo standard is /usr PYTHON_VERSION : defaults 2.2, we need to check and use the newer one Then bjam stage should provide us with neatly directoried stuff, which we'd mv into ${D} and just allow things to take their course. This should be much cleaner than the current implementation. I'm currently doing this by hand, just to make sure that all this actually works. Will report back, with ebuild if I can manage.
Created attachment 44920 [details] Initial attempt at ebuild This is my first attempt at an ebuild. It is very minimal. There needs to be support at different archs, and some cruft for installing the docs (based on USE="doc", obviously). It does, however, work in so far as installing the libs and header files. Note for those who seek to add to it: ${MAKEOPTS} is intentionally not used, as it seems to break the build by not copying libraries and symlinking; it may be possible to use -jN in the make (stage) tho, and -j1 in the install since the install goes over all the libs and copies them again. The dependency on Python could prob be left out, but considering we kinda depend on python on a fundamental level, it might be appropriate for gentoo nevertheless. Further work may be required if we want the entire Boost.Python suite to Just Work -- in particular we don't do anything for Pyste right now (I don't think gccxml and codependents are in portage anyway). Feedback would be appreciated.
That ebuild worked on amd64 too, but i had to change every occurance of the path tools/build/jam_src/bin.linuxx86/bjam to tools/build/jam_src/bin.linux/bjam I noticed that previous ebuilds used ${arch} at that point. The documentation is also missing in this ebuild. You could add the documentation installing part from older ebuilds.
Using what DieMumiee provided and adding Docs back in it seems to work fine. Please test, reopen if you find issues little tip for future ebuild submission: watch your headers, try to not drop the Gentoo Foundation and the newer license watch KEYWORDS, do not drop them only because you dont posses the hardware all stable archs should still be in the new ebuild with ~ in other words all archs in 1.31.0 should be in 1.32.0 with ~ added Thanks everyone
One little niggle. The install stage isn't using --layout=system, which gets rid of the 1_32 in the include and libs.
