Hi Jonathan, *,
On Mon, Apr 22, 2013 at 7:46 PM, Jonathan Aquilina
Rainer what i want to understand is why use an external build tool when
there is an equivalent to make built directly into visual studio.
You are completely missing the point here. The default build /does/
use Visual Studio Compiler, that is the default setup/the only
officially supported one to begin with.
mingw ist not a make system, but a compiler.
nmake is not a compiler, but a make-tool.
Replacing one by the other just doesn't work, since they do completely
LO uses gnu make as its make-tool since that is available to all
relevant systems and supports the features that are needed.
And if you're wondering why the build uses the Microsoft compiler instead:
It is a frequently asked question, usually coming from free software
purists, why we use proprietary compiler instead of a free one (e.g.
ABI backwards-compatibility for compiled extensions. There is some
resistance to breaking that - also so far MSVC produces faster,
There are also some features in the code that don't compile with
MinGW. They use API that MinGW does not provide headers for etc.
In addition to above points also there are also open questions around
how we would run unit tests in a MinGW cross-compilation environment
and how well gdb works on Windows; the MSVC C++ debugger is really
You're comparing apples and oranges. That just doesn't make any sense.
Unsubscribe instructions: E-mail to email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy