aboutsummaryrefslogtreecommitdiff
path: root/reproduce/software/make/build-rules.mk
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2019-10-29 13:23:42 +0000
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2019-10-29 13:27:51 +0000
commit97b511e71f4f63dfe2551460a6d3a04729948613 (patch)
tree612cb2218c55a64e1e95e30e3a3284d08dbe28cc /reproduce/software/make/build-rules.mk
parent1d4c587489cbb17c7ae9f6c0d0d5d919690fafde (diff)
Suggestion on good usage of /dev/shm in README-hacking.md
When you are working with large files and there is some good RAM in the system (large/powerful computers), it is beneficial to work in the shared memory directory and not the actual persistent storage (like HDD or SSD). With this commit, a fully working demo has been added to `README-hacking.md' (under the tips of "Make programming") to show how to effectively work in situations like this.
Diffstat (limited to 'reproduce/software/make/build-rules.mk')
0 files changed, 0 insertions, 0 deletions