mir/libreoffice
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updates

Browse Source
This commit is contained in:
Tor Lillqvist
2011-08-27 11:11:14 +03:00
parent 063a379307
commit d372bdadb9
1 changed files with 11 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
README.cross
View File

@@ -1,11 +1,13 @@
Cross-compiling LibreOffice Cross-compiling LibreOffice
=========================== ===========================
Notes on cross-compiling LibreOffice, written by Tor Lillqvist Notes on cross-compiling LibreOffice, originally written by Tor
<tlillqvist@novell.com> <tml@iki.fi> in May, 2011. Lillqvist <tlillqvist@novell.com> <tml@iki.fi> in May, 2011, for later
history see git log.
Cross-compilation of LibreOffice is not possible yet. Some initial Cross-compilation of LibreOffice completely is not possible yet. Much
work is done, "baby steps", but a lot remains. This work is highly work has been done, "baby steps" for some platforms, much more for
others, but a lot remains. For iOS and Android this work is highly
experimental and done mostly in my own spare time just for the hacking experimental and done mostly in my own spare time just for the hacking
pleasure. No promise, explicit or implied, is given that it will ever pleasure. No promise, explicit or implied, is given that it will ever
be finished. be finished.
@@ -69,10 +71,11 @@ attempted cross-compilation.
This OOo-originated MinGW support attempts to support both running This OOo-originated MinGW support attempts to support both running
Cygwin gcc in its -mno-cygwin mode, and a native MinGW compiler. The Cygwin gcc in its -mno-cygwin mode, and a native MinGW compiler. The
-mno-cygwin mechanism in the Cygwin gcc is rapidly being obsoleted, if -mno-cygwin mechanism in the Cygwin gcc is rapidly being obsoleted, if
it isn't already, and I have not attempted to check that it keeps it isn't already, and I have not attempted to try to keep it working;
working. Ditto for native MinGW; if one compiles natively on Windows, in fact I have activly cleaned out mechanisms related to this. Ditto
why not use Microsoft's compiler, as OOo/LO has been build for Windows for native MinGW. If one compiles natively on Windows, just use
all the time using that and it works fine. Microsoft's compiler. OOo/LO has been built for Windows all the time
using that.
In my opinion, the only case where it makes sense to use MinGW is for In my opinion, the only case where it makes sense to use MinGW is for
cross-compilation. There is just too much crack on Windows anyway, and cross-compilation. There is just too much crack on Windows anyway, and