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


Jonathan Aquilina wrote
Joel we are really complicating things with mingw when all one would need
to do is install visual studio and run nmake from its command line and you
are good to go.

Because MinGW is an Open Source compiler and Visual Studio is a closed
source, commercial compiler which has a free limited version. Using Visual
Studio is a courtesy (which could stop at any time). Using an Open Source
tool to build an Open Source program makes ALL sense.

(unfortunately Jan Holesovsky aka Kendy from Suse, who set up and maintains
the  MinGW tinderbox seems to have his hands full with other stuff)

See these old topics about MinGW
http://nabble.documentfoundation.org/Compiling-in-Windows-td1792684.html

and

http://nabble.documentfoundation.org/MinGW-master-build-td3400162.html



--
View this message in context: 
http://nabble.documentfoundation.org/NMake-vs-MinGW-tp4051639p4051704.html
Sent from the Discuss mailing list archive at Nabble.com.

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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

Context


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.