Differences

This shows you the differences between two versions of the page.

--- compile_batocera.linux [2025/06/30 03:05] – remove direct compilation instructions (does not work currently) atari
+++ compile_batocera.linux [2026/04/03 02:04] (current) – dmanlfc
@@ Line 133: / Line 133: @@
 <code bash>
-make batocera-docker-image
+make build-docker-image
 </code>
@@ Line 179: / Line 179: @@
 <code bash>
 make x86_64-build
+</code>
+If you have a lot of cores/threads on your compilation CPU, and enough RAM to support it, you can accelerate the compilation time by parallelizing package builds with:
+<code bash>
+PARALLEL_BUILD=1 make x86_64-build
 </code>
@@ Line 275: / Line 281: @@
 Of course ''x86_64'' is an example in the commands above, you can use any supported arch.
-==== Traditional compilation method ====
-Of course you can still use out of tree builds to compile Batocera. So, for x86_64, you can do the following:
-<code bash>
-make O=$PWD/output/x86_64 BR2_EXTERNAL=$PWD -C $PWD/buildroot batocera-x86_64_defconfig
-cd output/x86_64
-make
-</code>
-Source tree will stay pristine and we be reused for other builds following the same procedure with a different output directory. For example:
-<code bash>
-make O=$PWD/output/rpi3 BR2_EXTERNAL=$PWD -C $PWD/buildroot batocera-rpi3_defconfig
-cd output/rpi3
-make
-</code>
-Then, you can take some time for a coffee (or two, or two hundreds actually). Depending on how powerful your CPU is, how much RAM you have, and how fast your SSD/HDD is, compiling a whole Batocera system can take many hours. Don't forget, it's the full OS with all the emulators that we are compiling here, it's not a small task.
-Please also mind that the process will take a significant amount of space, **so ensure to have between 50GB (RPi) and 150+GB (x86_64) of free space on that partition**.
 ===== Locating the image =====