Ok so I've pushed a feature/gnumake2 branch.
It contain about half of the gnumake2 CWS plus few adjustment due to
the fact that things have changed in our trees.
I pushed at this point because:
1/ the regular build still function fully using the old method. and
the modules "framework ooo sfx2 svl svtools sw toolkit tools xmloff"
build successfully with the new gnumake system.
2/ I ran into a stretch of patches that rely on CWS sb139 being
merged ( this implement a fix to
http://qa.openoffice.org/issues/show_bug.cgi?id=113189 'passive
registration of UNO components' )
that CWS had been merged into DEV300_m89. It is 15 or so commits, some
of them massive( one is a 1.5MB patch) and is addressing a problem I
know nothing about (yeah, I know... one day I need to find a way to
grasp that UNO thing :-) ).
Furthermore that also create a new module (xmlreader) which need to be
assigned a git repository
All that lead me to conclude that it would be wiser to wait and see
what we do with m89 (kendy?), wait for it to be merged/cherry picked
and then resume merging the rest of gnumake2
3/ I've done things on Linux so far. I'll be able to pull on MacOS and
iron the problem there.... As usual Windows will have to be left as an
exercise to the reader.
Norbert.
PS: not that it is very meaningful but:
in sw, on a Quad-core, witch ccache (all runs fully cached)
time build -P4 -- -P4
real 1m47.932s
user 3m26.171s
sys 1m7.191s
time make -sr -j16
real 1m0.491s
user 2m15.087s
sys 1m14.152s
time build -P5
real 3m9.136s
user 3m18.709s
sys 1m1.109s
time make -sr -j5
real 1m2.303s
user 2m12.577s
sys 1m10.531s
Context
- [Libreoffice] GnuMake · Norbert Thiebaud
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.