Hullo LibO Devs,
In a search of my build.log for libuno_sal, the first reference I see
points me to lines that look line this (newlines added for email clarity):
-----
rm -f ../unxlngx6/lib/check_libuno_sal.so.3
mv ../unxlngx6/lib/libuno_sal.so.3 ../unxlngx6/lib/check_libuno_sal.so.3
[...]/solenv/bin/checkdll.sh [...] ../unxlngx6/lib/check_libuno_sal.so.3
rm -f ../unxlngx6/lib/libuno_sal.so
cd ../unxlngx6/lib && ln -s libuno_sal.so.3 libuno_sal.so
Making: libuno_sal.so.3
ccache g++ [...] -o ../unxlngx6/lib/libuno_sal.so.3 [...]
-----
Question: if we're making libuno_sal.so.3 afresh, what's the rational to
bother performing various checks on it prior to making it?
Further, I don't see where the first line's reference to
check_libuno_sal.so.3 comes from. i.e. When did it get built prior?
Similar question goes for line 2 above (mv ...).
In a very similar vein, I see lots of this paradigm:
...
rm -f path/to/file
gcc -o path/to/file [...]
...
That gcc command will just overwrite the file if it's there, no?
Therefore, why execute rm?
Thanks,
Kevin
Context
- [Libreoffice] unnecessary build actions? · Kevin Hunter
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.