Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Re: [tdf-discuss] Re: Will win64 native build exist on 3.5.0 or at least 3.5.x releases?

Hi Pedro,

Il 02/11/2011 13:19, Pedro ha scritto:
In my opinion TDF and LibreOffice should abandon the MS compiler and support
the switch to MinGW which has already been started by Jan Holesovsky (aka

I think we could put here, at least, the links:

for interested people...

This would also open the path to using MinGW64 and therefore the creation of
a native 64bit version of LO...

I follow some and various FLOSS projects that are both and natively win32/win64 like these:   (If I don't remember wrong, it use MinGW.) and

and some that try to go win64 too, but without official courage, bravery, fearlessness

and some that are not trying at all

Could we understand and learn somethings from above projects' choices and code?

The fact that it is a requirement to use a specific proprietary compiler to
compile a FLOSS program makes the same sense as offering a free complete car
(wheels, tires, etc) but to assemble it you would need to buy a wrench which
is sold by a single company...

There are pros and cons to use Microsoft native and MinGW/GW64 compilers and libs, I suppose.

Just my 2 cents.
Have a nice evening,


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.