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


Le 15/01/13 14:59, Tom Davies a écrit :
Hi :)
Is it worth learning how to compile from source in order to get one tailored to your system?  

IMHO, yes, it is an interesting, if sometimes rather frustrating,
experience for a non-developer/casual software builder.


On the other hand i gather it ties-up a desktop machine for quite a
while so if you don't have access to several machines then it might be a
pain.

Building does indeed take a while, on my 4gig RAM Linux box, about 10 -
12 hours, sometimes more if there are lots of changes in the git repo.


I keep being told that compiling is "really not difficult" but it still scares me.  

Nothing to be scared about. It won't trash your machine (but might make
the GUI unusable if you don't have much RAM). Patience is definitely a
virtue when it comes to building LO. It is just that when the build
fails, there's not always an obvious explanation for why, especially if
it built fine previously for several days, or even months.


Alex



-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.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.libreoffice.org/global/users/
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.