forked from amazingfate/loongoffice
5acbd4b5f5
in case the script is aborted/fails otherwise and doesn't remove the lockfile, another attempt to obtain the lock ends up in an endless loop No problem if the user sees the corresponing messages, but when using shell redirection of stdout and stderr and trying to tee that to a logfile, the message is never seen/the buffers are not flushed So force flushing stdout to have the message show up in the terminal Change-Id: Ib133b9bc523d9ba2210564f75762258f41415f71 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/182595 Tested-by: Jenkins Reviewed-by: Xisco Fauli <xiscofauli@libreoffice.org> Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com> (cherry picked from commit 55b13db9f18a945bb5e61e14a462f5770ce99d66) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/182618
Tools and Non-Build Scripts
Tools and scripts mostly not used during the build
This direction has a number of key pieces (?) that are used during the
build, or are simply generally useful. One example is bin/run.
This utility can be used to run the executables in this folder:
workdir/LinkTarget/Executable
Format of the usage is:
./bin/run application [parameters]|--list|--help
Use --list (same as -list or -l) to get the list of executables Use --help (same as -help or -h) to get this help
Another example is:
bin/find-german-comments <directory>
which will try to detect and extract all the German comments in a
given source code hierarchy / directory.
Please note that the associated issue tdf#39468 is now marked as RESOLVED/FIXED, so don't expect many German comments.