maria-developers team mailing list archive
Mailing list archive
Re: Status of Windows build
Not being a build/packaging expert, there are two issues here:
- Making it possible for any developer to build (and develop)
MariaDB on Windows with Visual C++. This is perfectly possible
with either edition of Visual C++.
- Creating a binary distribution for direct installation. This is
the issue we are discussing.
I spent half an hour searching MS web site for a comparison of
the versions, and Bo seems right - no differences are claimed
with respect to the optimizing compiler.
The major two differences I found in the VC++ 2008 that affect
A) The Express Edition cannot build 64-bit binaries.
B) The Express Edition has much fewer tools to create binary
To me (A) is the more important one, and (B) needs to be
investigated. Since Sergey Petrunia built the binaries so far,
I hope he can tell whether what's missing in the Express Edition
is needed or not.
My source of information is this page:
[moving the discussion to maria-developers@]
Timour Katchaounov <timour@xxxxxxxxxxxx> writes:
1. buy VS Enterprise Edition (or Standard Edition, I wasn't able to figure out
what exactly do we need to make builds. They don't offer evaluation versions of
Standard, only Enterprise).
2. make the build script support building with VS Community Edition (possible
but will take some time).
No, we should not build with VS Community Edition. AFAIK, the free edition's
compiler produces much less optimized code than the payed for editions. I don't
think it is serious on our side to save money by not buying one VS license.
On the other hand, the advantage of building with the community edition (I
think we really mean the express / no-cost edition right?) is that it makes it
easier for people to build themselves (and get the same result as our release
builds). This is IMO important, we are an Open Source project after all.
So it would be interesting to learn if there really is a speed difference
here. Do you have some background information on this? Or do we need to run
benchmarks to know for sure?
One more alternative would be to create a Windows virtual machine, and install
the evaluation version in the VM. Then once there is a copy, one can always
roll-back to the "fresh" installation.
Given what is at stake, I'd much prefer that we have a license of VS.
As I said above, I would prefer using the no-cost version, unless there is a
real reason not to.
Just my 2 cents,