{"id":3506,"date":"2024-12-05T22:28:46","date_gmt":"2024-12-05T21:28:46","guid":{"rendered":"http:\/\/vizZzion.org\/blog\/?p=3506"},"modified":"2024-12-05T23:14:26","modified_gmt":"2024-12-05T22:14:26","slug":"icecream","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2024\/12\/icecream\/","title":{"rendered":"icecream!"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Lots of KDE hacking these days, and that comes with compiling large amounts of code. Right now, I am installing, well building from source <a href=\"https:\/\/plasma-mobile.org\/\">Plasma Mobile<\/a> on an &#8220;old&#8221; laptop so I can test some patches natively on a touchscreen device. The machine has just two cores (hyperthreaded), so builds take rather long, especially if you build Qt and all that 80+ packages that are needed for a fully working Plasma system.<br>One of the tools that do an incredible job while being super flexible to use is <a href=\"https:\/\/github.com\/icecc\/icecream\">icecream<\/a>. Icecream (or &#8220;<code>icecc<\/code>&#8220;) allows you to distribute your build over multiple machines, it basically ships compile-jobs with all that&#8217;s needed to other machines on a local network, meaning you can parallelize your builds. <\/p>\n\n\n\n<p class=\"has-text-align-center wp-block-paragraph\"><a href=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2024\/12\/icecc.png\"><img loading=\"lazy\" decoding=\"async\" width=\"400\" height=\"253\" class=\"wp-image-3510\" style=\"width: 400px;\" src=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2024\/12\/icecc-small.png\" alt=\"\" srcset=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2024\/12\/icecc-small.png 400w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2024\/12\/icecc-small-300x190.png 300w\" sizes=\"auto, (max-width: 400px) 100vw, 400px\" \/><\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Icecream has this nice visualization tool, called <code>icecream-monitor<\/code> which you can stare at while your builds are running (in case you don&#8217;t have anyone handy for a <a href=\"https:\/\/xkcd.com\/303\/\">sword-fight<\/a>). In the screenshot you can see <code>manta<\/code>, the underpowered laptop doing a 32 parallel job build over the network. <code>miro<\/code> is my heavy workstation, 8 cores and 128GB of RAM, it duely gets the bulk of the work assigned, <code>frame<\/code> is my (<a href=\"https:\/\/frame.work\/nl\/en\/products\/laptop13-diy-intel-ultra-1\">Framework<\/a>) laptop, which is also quite beefy, gets something to do too, but not taxed as heavily as that build monster in my basement office.<br>Icecream can be used with most environments that have you run your compiler locally. Different distros are no problem! Just a matching CPU architecture is needed. Icecream does its job by providing its own <code>g++<\/code> and <code>gcc<\/code> binaries, which will relay the build jobs transparently to either your local machine or across the network. So you basically install it, adjust your <code>PATH<\/code> variable to make sure icecc&#8217;s <code>g++<\/code> is found before your system&#8217;s compiler and start your build. Other machines you want to join in for the fun just need to run <code>icecc-scheduler<\/code> and they will be automatically discovered as build slaves on your network. If you want to further speed up builds, it works with <code>ccache<\/code> as well.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Please note that you only want to do this in a trusted environment, we&#8217;re shipping executables around the network without authorization!<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Lots of KDE hacking these days, and that comes with compiling large amounts of code. Right now, I am installing, well building from source Plasma Mobile on an &#8220;old&#8221; laptop so I can test some patches natively on a touchscreen device. The machine has just two cores (hyperthreaded), so builds take rather long, especially if&hellip; <a class=\"more-link\" href=\"https:\/\/vizZzion.org\/blog\/2024\/12\/icecream\/\">Continue reading <span class=\"screen-reader-text\">icecream!<\/span> <span class=\"meta-nav\" aria-hidden=\"true\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":3510,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,29,25,28,32,35],"tags":[],"class_list":["post-3506","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-english","category-kde","category-linux","category-mobile","category-plasma","category-qt"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/3506","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/comments?post=3506"}],"version-history":[{"count":9,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/3506\/revisions"}],"predecessor-version":[{"id":3521,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/3506\/revisions\/3521"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media\/3510"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=3506"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=3506"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=3506"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}