Le vendredi 18 mai, Volker Braun a écrit: > I just had a look at boost, if we delete the documentation then it is > 25MB. Without documentation and tests it is 15MB, though I'd rather > have the tests included. > > Although most of boost is headers, some libraries need to be > compiled. The biggest question is probably if we want to build > boost/Python, which is roughly the inverse of Cython: write Python > objects in C++. > > Boost/Math/Special functions might be useful to avoid the > shortcomings of the libc implementations on some platforms.
The current boost_cropped contains headers, nothing compiled. My proposition is mostly to replace a bunch of headers described by the rather cryptic "Split boost sources off of polybori.spkg" (Are they all of boost-1.34.1 upstream? Only a part? Which part? Which version of the polybori spkg was it?), by a bunch of headers taken directly from upstream with an explicit list of what was taken "The package contains the following directories taken from boost version 1.49.0 : ...". Notice that boost is in sage for polybori, and polybori is compiled with no boost-python support (from custom.py, in the current polybori spkg): HAVE_PYTHON_EXTENSION=False EXTERNAL_PYTHON_EXTENSION=True Snark on #sagemath -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
