[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql-plusplus
Subject:    Re: Next MySQL++ build system
From:       Pau Garcia i Quiles <pgquiles () elpauer ! org>
Date:       2014-01-09 18:59:56
Message-ID: CAKcBoksX0tROoNoisdawuDL4wvXAb9OeDd9uwLkSP5xPFJo0rw () mail ! gmail ! com
[Download RAW message or body]


On Thu, Jan 9, 2014 at 6:47 PM, Warren Young <mysqlpp@etr-usa.com> wrote:


> > Visual C++ does not provide any C++ ABI compatibility whatsoever.
>
> That pretty much kills any option for a VC++ binary package, then.
>  MySQL++ currently works on ten different versions of VC++, if you count
> 32- and 64-bit binaries separately.  I'm missing at least two of the
> compilers necessary to produce all of those binaries -- 64-bit versions of
> VS2010 and 2012.
>
> I could go eBay some disused copies of VS2010 and 2012, but I'm not
> feeling compelled to spend the time and money.
>
> It probably isn't worth the bother.  As has been pointed out in this
> thread, if a developer wanting to use MySQL++ can't figure out how to build
> MySQL++, they have bigger problems than the out-of-the-box usability of
> MySQL++.
>
>
False dichotomy ;-)

IMHO there is no need to provide binaries for EVERY version of MSVC that
could be used, but only for the most "popular". Or even only the ones you
feel like providing. E. g. MSVC2010 32-bit, MVSC2012 32-bit and MSVC2013 32
and 64-bit. Or even less than that.

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)


[prev in list] [next in list] [prev in thread] [next in thread]