From time to time when we update LAC, we may be delayed before publishing the Raspberry Pi version. This need NOT delay Raspberry Pi fans. You can compile your own Raspberry Pi version from any of our tar.gz archives that include source code. Our Raspberry Pi compiling process is well documented here:
You must make just ONE change to the source code in order to get it optimized for the Raspberry Pi: Edit the "common.h" file and change THIS line of code:
// #define RASPBIAN // Raspberry Pi requires a few tweaks. Define RASPBIAN to activate them or comment this line out.
to THIS:
#define RASPBIAN // Raspberry Pi requires a few tweaks. Define RASPBIAN to activate them or comment this line out.
As you can see, you just need to delete the two slash bars to "uncomment" (or activate) that line of code, which instructs the compiler to compile for the Raspberry Pi.
Last edit: bbosen 2023-02-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
From time to time when we update LAC, we may be delayed before publishing the Raspberry Pi version. This need NOT delay Raspberry Pi fans. You can compile your own Raspberry Pi version from any of our tar.gz archives that include source code. Our Raspberry Pi compiling process is well documented here:
https://askmisterwizard.com/2019/LinuxAirCombat/LacOnRaspberryPi.htm
You must make just ONE change to the source code in order to get it optimized for the Raspberry Pi: Edit the "common.h" file and change THIS line of code:
// #define RASPBIAN // Raspberry Pi requires a few tweaks. Define RASPBIAN to activate them or comment this line out.
to THIS:
#define RASPBIAN // Raspberry Pi requires a few tweaks. Define RASPBIAN to activate them or comment this line out.
As you can see, you just need to delete the two slash bars to "uncomment" (or activate) that line of code, which instructs the compiler to compile for the Raspberry Pi.
Last edit: bbosen 2023-02-06