Files
loongoffice/bin
Luboš Luňák f5fa61e7f0 add PCHs for more external libs
I think this is all external libs where it makes sense for them
to have their own PCH and be worth it. Maybe some smaller externals
can also use the common system PCH, but unfortunately many externals
use all kinds of defines that affect system headers, which is
a problem for the common system PCH.

Change-Id: I2c589ac55d93728daf3b158df110722e5f055d45
Reviewed-on: https://gerrit.libreoffice.org/80728
Tested-by: Jenkins
Reviewed-by: Luboš Luňák <l.lunak@collabora.com>
2019-10-14 11:07:30 +02:00
..
2019-09-30 16:53:32 +02:00
2019-01-28 09:17:03 +01:00
2019-09-30 16:53:32 +02:00
2019-04-10 07:36:25 +02:00
2019-08-01 20:08:08 +02:00
2019-09-30 16:53:32 +02:00
2018-12-19 08:02:27 +01:00
2018-12-25 10:14:24 +01:00
2019-10-14 11:07:30 +02:00
2019-10-14 11:07:30 +02:00

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/find-german-comments <directory>

which will try to detect and extract all the German comments in a
given source code hierarchy / directory.