Macintosh-HW/RASCSI
1
0
Fork 0
mirror of https://github.com/akuker/RASCSI.git synced 2024-09-27 15:57:52 +00:00
Code Issues Projects Releases Wiki Activity

Updated Setup Instructions (mediawiki)

Uwe Seimet 2022-09-04 12:33:28 +02:00
parent 17b1d284f3
commit d1fbc800fd
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Setup-Instructions.mediawiki

@ -176,15 +176,16 @@ To explicitly build for ARM (ARM is also the default, so this shouldn't be neces
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
```
= Compiling on Raspberry Pi OS 11 or on x86/x86_64 with the Eclipse IDE (CDT) =
= Compiling on x86/x86_64 Linux PCs with the Eclipse IDE (CDT) =
Eclipse does not create executable ARM binaries but is useful because it compiles fast and helps with browsing and refactoring the C++ sources. In addition, rasctl can be run on a different computer than the Pi (essentially on any Linux PC) and can access rascsi on the Pi remotely.
With these C++ environment settings the code compiles on Raspberry Pi OS 11 or an x86/x86_64 PC, and also compiles with Eclipse CDT:
Using the Eclipse IDE for development helps with browsing, refactoring and unit-testing the C++ code. The SonarLint plugin helps with working on code quality issues reported by SonarCloud.
A lot of the rascsi code does not require the RaSCSI hardware and can be run and tested on a regular Linux PC. rasctl can be run on a Linux PC without restrictions and can access rascsi on the Pi remotely.
With these C++ environment settings the complete code compiles with g++ or clang++ on x86/x86_64 PCs, and also compiles with Eclipse CDT:
```
CROSS_COMPILE= (empty)
DEBUG=1
EXTRA_FLAGS=-DSPDLOG_FMT_EXTERNAL -DFMT_HEADER_ONLY
EXTRA_FLAGS="-DSPDLOG_FMT_EXTERNAL -DFMT_HEADER_ONLY"
```
<!--