summaryrefslogtreecommitdiffstats
path: root/libraries/qt5-legacy/README.ccache
diff options
context:
space:
mode:
author Dave Woodfall <dave@slackbuilds.org>2020-04-06 00:50:54 +0100
committer Dave Woodfall <dave@slackbuilds.org>2020-04-06 04:09:17 +0100
commit1c4cb7751c0fc256154bde487b02605a45133282 (patch)
tree81f921b0ea787c543c2cd5bb3e9d7b726032049e /libraries/qt5-legacy/README.ccache
parent439e402d43c27f19205c969909f10657d201b720 (diff)
downloadslackbuilds-1c4cb7751c0fc256154bde487b02605a45133282.tar.gz
slackbuilds-1c4cb7751c0fc256154bde487b02605a45133282.tar.xz
libraries/qt5-legacy: Update to 5.9.9.
Diffstat (limited to 'libraries/qt5-legacy/README.ccache')
-rw-r--r--libraries/qt5-legacy/README.ccache46
1 files changed, 46 insertions, 0 deletions
diff --git a/libraries/qt5-legacy/README.ccache b/libraries/qt5-legacy/README.ccache
new file mode 100644
index 0000000000..1053bcc5c9
--- /dev/null
+++ b/libraries/qt5-legacy/README.ccache
@@ -0,0 +1,46 @@
+NOTES ON SETTING UP CCACHE
+
+Using ccache can save a lot of time when building packages,
+and this is not limited to Qt5. Ccache is installed by
+default on stock Slackware.
+
+ccache(1) has a lot of useful info on using ccache, however
+I don't recommend using its method of symlinking. Instead I
+recommend the following way:
+
+mkdir -p /usr/local/bin
+ln -s /usr/bin/ccache /usr/local/bin/cc
+ln -s /usr/bin/ccache /usr/local/bin/c++
+ln -s /usr/bin/ccache /usr/local/bin/gcc
+ln -s /usr/bin/ccache /usr/local/bin/g++
+
+Doing it this way rather than copying the ccache binary as
+the man page suggests will ensure that the ccache used is
+updated whenever the ccache package is.
+
+The cache is created in the home directory of the user using
+it, and since slackbuilds are run by root that will be in
+/root/.ccache, therefore ensure that you have enough free
+space on the root file system for it. It is possible to put
+the cache directory elsewhere though. See the man page for
+info. But it would probably be fastest when on the same
+file system as the build directory.
+
+It's also possible to host the cache on a shared NFS
+directory, but be sure to test the speed before committing
+to that. The man page has some notes on this.
+
+Since Qt5 can take a lot of build space I recommend a max
+cache size of AT LEAST 6 GB. If you intend to use it all
+the time then use as much as you can. The default size is
+5 GB. I use 20 GB on my main build box, but use 7 GB on
+workstations and servers.
+
+Handy commands:
+
+ccache -s: To show some statistics.
+ccache -M <N>: To set the max cache size to N.
+
+(use G for GB with -M.)
+
+Last updated Mon 10 Dec 03:46:41 UTC 2018