Re: [boost] Pre-build MSVC Boost binaries

Subject: Re: [boost] Pre-build MSVC Boost binaries
From: Tom Kent (lists_at_[hidden])
Date: 2013-08-01 22:30:22

I'd be happy to join forces!

For the last several versions I was just posting them to my personal
website, but with this release (and the closing of BoostPro with their
windows binary installer) we made my builds available in the same place as
the official source releases.

I think that should be the place we should direct people to for windows
binaries, be it the ones I'm currently building or the ones that come from
your project.

I've never actually used the python (or zlib bzlib) functionality, so I
wasn't aware there were version dependencies that needed to be noted there,
but I can definitely add that to my releases. The only thing I'd like to
avoid is doing multiple builds for something like this. I'm already doing
one for each Visual C version, I wouldn't want to have the double or triple
for each python.

I do, however, already provide both the static and shared library builds in
all the various versions/architectures.

This is the main script that I use for all my builds.
https://github.com/teeks99/boost-build/blob/master/BoostBuilding/BuildOneRelease.bat

Let me know what you think.

Tom

On Wed, Jul 31, 2013 at 8:22 AM, Fredrik Orderud <forderud_at_[hidden]> wrote:

> Over the last year, I've set up a small SourceForge "WinBin" project [1]
> for distributing Microsoft Windows binaries for Boost (and some other
> projects). The repository is sorted by Boost version, compiler version and
> shared vs. static linking. Each file archive contains pre-build boost in
> debug/release for both 32/64-bit, following a include/lib[64]/bin[64]
> folder structure.
>
> There also seems to be some other sources for pre-built boost around (e.g.
> https://sourceforge.net/projects/boost/files/boost-binaries/ and
> http://boost.teeks99.com/bin/). However, these do not seem to provide
> boost
> built for both static and shared linking. Also, they do not appear to
> adhere to the "quasi standard" include/lib[64]/bin[64] folder naming
> convention used by many libraries. Finally, they seem to lack information
> on which version of python (and possibly other 3rd party SW) they are
> compiled against. Therefore, I decided to set up my own boost-binaries
> webpage.
>
> Please let me know if you might be interested in either improving the
> "WinBin" project, or somehow joining forces to merge the various sources of
> Boost binaries into a single, more "authoritative" repository. I would be
> more than happy to shut WinBin down if "similar enough" binaries can be
> downloaded elsewhere.
>
> Thanks in advance,
> Fredrik Orderud
>
> [1] https://sourceforge.net/projects/winbin/files/boost/
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>