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


On 08.01.2019 10:44, Komal Bharadiya wrote:
I have been trying to setup libreoffice dev-environment lately. After 
executing ./autogen.sh file, I hit make command. The execution takes 
ample amount of time. It hangs my laptop, and I end up switching it off. 
I have tried multiple no. of times. But couldn't run it successfully, 
what can I do? Please help!
I have Dell Vostro 3568 model.
Thanking you in anticipation!

https://wiki.documentfoundation.org/Development/BuildingOnLinux#Performance


Building LibreOffice takes time, a lot of time. Exactly how much depends on how powerful your 
machine is

Several lines below, there's "Approximate times" section, telling 
someone's experience with some unspecified repo revision, which took 1.5 
hrs. I can tell you that I used to have ~8 hrs build time on Kaveri 7700 
box with spinning HDD.

You should expect long build times on your laptop. But if you also are 
going to do other tasks on it during the build (to increase build times 
even more), then you may adjust it using --with-parallelism (discussed 
there), which defaults to use all your cores, but which you could want 
to set to a lower value to free some resources; or you may run make 
using nice (`nice make`) to decrease its priority and make system 
responsive to interaction without sacrificing cores.

-- 
Best regards,
Mike Kaganski

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.