[FEAT] Kindle building documentation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c, cmake
- Domain
- build-system, documentation
Research direction
Start with the supplied CMake command and check the README or Wiki for existing build instructions. Confirm the Kindle-specific prerequisites and which options are needed for the described build; done means readers can follow the documentation to build Fastfetch for a jailbroken Kindle using fclang.
Written by the indexing model from the issue text.
Description
Description
Hi, I managed to get Fastfetch to build natively for a Kindle Paperwhite using a wrapper I made for Clang called fclang. It would be interesting if you could add documentation for how to build Fastfetch using CMake and fclang with clang to the Wiki or README or whereever.
Motivation
Because I'm not really a fan of the alternative (KindleFetch) program. I just prefer the amount of tools that are in fastfetch instead.
Additional context
I managed to build it using:
mkdir -p build && cd build
cmake .. \
-DCMAKE_C_COMPILER=fclang \
-DCMAKE_SYSTEM_NAME=Linux \
-DCMAKE_SYSTEM_PROCESSOR=arm \
-DENABLE_VULKAN=OFF \
-DENABLE_OPENCL=OFF \
-DENABLE_SQLITE3=OFF \
-DENABLE_CHAFA=OFF \
-DENABLE_DBUS=OFF \
-DBUILD_TESTS=OFF
make -j$(nproc)
On my Debian machine. As mentioned in fclang, I did have to do some package installing to get it working on my Kindle Paperwhite 1 (specifically installing the libc armel architecture packages from apt on Debian latest).
And this is only possible using a jailbroken Kindle. Otherwise, it's impossible to run programs on a Kindle natively.
I don't think it's possible without changes to the CMake configuration to build this without my Clang wrapper fclang. This is because it changes the compiler --target variable which I'm mostly sure CMake doesn't do properly. fclang also has presets specifically for different versions of Kindle devices, so it may be possible to get fastfetch to work properly on other Kindles as well.
- Dominant language
- C
- Stars
- 25.1k
- Forks
- 928
- Avg merge
- 16h 40m
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fastfetch-cli/fastfetch
-
logo request
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
fastfetch-cli/fastfetch#2661 ·
Maintainers usually reply within 1 day
-
[LOGO] kairo linuxOpenlogo request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fastfetch-cli/fastfetch#2650 · 1 comment ·
Maintainers usually reply within 1 day
-
[LOGO] Keenetic OSPossibly taken @Ivan-Alone claimed this 12 days ago. Openlogo request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fastfetch-cli/fastfetch#2646 ·
Maintainers usually reply within 1 day
-
[LOGO] Darkian LinuxPossibly taken @lordpipon claimed this 13 days ago. Openlogo request
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
fastfetch-cli/fastfetch#2644 ·
Maintainers usually reply within 1 day
-
[LOGO] ArmadaOSPossibly taken @Tyagiquamar claimed this 10 days ago. Openlogo request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fastfetch-cli/fastfetch#2641 ·
Maintainers usually reply within 1 day
All issues in fastfetch-cli/fastfetch
Similar issues
-
v9.6.0: CMake incorrectly enforces presence of libevdevPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
[Bug] Unhandled ValueError terminates watchdog thread when GISRC value contains multiple colonsOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug Component component: net
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RT-Thread/rt-thread#11913 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
contiki-ng/contiki-ng#3289 ·
Maintainers usually reply within 3 days
-
area:docs help wanted type:enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day