Assuming that we will try to ditch MSVC in favor of mingw on Windows,
Not MinGW on Windows, but MinGW as cross-compiler from Linux (or from
some other Unix).
If you are building *on* Windows, use MSVC, is my opinion. OOo thinks
differently; they do/did try to support compiling using MinGW on
Windows (and they haven't done any cross-compilation efforts at all
AFAIK).
will we require people hacking on Windows to use mingw exclusively?
I don't think we want to intentionally prevent the code from building
with MSVC, even when at 4.0 we (hopefully) start distributing a
cross-compiled build.
Also, does mingw do platform specific optimization as well as MSVC does?
No idea, presumably not.
How will one debug LibreOffice on Windows?
gdb? Yeah, horrible in many ways compared to Visual Studio.
I assume using Visual Studio as a debugging tool is out the window (no
pun intended)?
I *think* I have heard people talk about some add-on trick to make
Visual Studio understand also MInGW-generated debugging info.
--tml
Context
Re: [Libreoffice] oox/source/drawingml/customshapepresets.cxx is just too much for gcc · Bjoern Michaelsen
Re: [Libreoffice] oox/source/drawingml/customshapepresets.cxx is just too much for gcc (rant inside) · Bjoern Michaelsen
Privacy Policy |
Impressum (Legal Info) |
Copyright information: 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.