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


On Monday 16 of April 2012, Matúš Kukan wrote:
On 16 April 2012 18:23, Lubos Lunak <l.lunak@suse.cz> wrote:
 It is made even worse by the fact that make+gbuild order build commands
so that allmost all compiles go first and linking goes last

As I've seen complaining about this, I was thinking..
Now, when sw links against svx, make starts compiling sw's sources
after header files related to svx are in solver. (Because sw most
probably includes them.)
We can change that so sw would also wait on library svx. and only then
start building.
I am not sure how much would that hurt parallelism but maybe not that
much and it could be improvement in the sense of ordering?

 I don't think it would hurt parallelism much, because the linking of svx 
needs to be done somewhen, and make should have enough of other stuff to do. 
On the other hand, I doubt such one change would change much. Could gbuild be 
changed so that each library target depends on its dependent libraries not 
only for linking, but also for compiling its sources? That would essentially 
change it to be like recursive make, but without the disadvantages (that's 
how cmake builds in practice, and there seems to be always enough to 
compile).

 Other option I've been thinking of is simply patching our make to be smarter 
about selecting the next target to build.

-- 
 Lubos Lunak
 l.lunak@suse.cz

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.