buildroot
riscv-gnu-toolchain
Our great sponsors
buildroot | riscv-gnu-toolchain | |
---|---|---|
51 | 35 | |
2,476 | 3,121 | |
2.9% | 4.2% | |
10.0 | 8.2 | |
4 days ago | 4 days ago | |
Makefile | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
buildroot
- Damn Small Linux 2024
-
I Built Linux from Scratch
I did it few times. It's so much easier nowadays with https://buildroot.org/
-
GitHub - avxmw/creality_k1_fw: Tracks firmware for Creality K1 series 3D printers
If you dig through the rootfs of the K1 it becomes clear that Creality is using buildroot so we should be able to do that ourselves - at least some of us.
- Fazer uma distribuição Linux
-
Curious about Roku OS
An embedded system like Roku doesn't need to "run everything", it just needs to run their "platform", which is probably quite small. It's pretty trivial to assemble your own OS from "off-the-shelf" components. You can use something like buildroot to spin up a new OS in half a day, using only the components you want. You can also use "smaller" components that have far fewer features, meaning less bugs and less updates.
-
Linux-factory: A framework used to create custom Linux Debian operating systems
https://github.com/buildroot/buildroot
-
Debloating Windows 10 with one command and no internet scripts
> I do this for every Windows installation that is used for similar purposes, like embedded machines that has to run a single application, virtual machines, etc.
Have you tried running Linux for these use cases? This sort of thing is an area Linux excels, in my experience.
When you run Windows, you're in for the whole kit and caboodle. Most of the components are proprietary, closed-source black boxes. You can only poke and prod and test and hope things don't break in unexpected ways.
Conversely, Linux can be easy stripped down to a bare bones kernel and a single statically-linked binary. I can run a useful application on top of Linux with the whole system weighing in smaller than bootmgfw.efi.
Something more complex, but still custom, is easily crafted with Buildroot.
https://buildroot.org/
-
Automatically generate commit messages using ChatGPT
Have a look at the commit history of Linux or buildroot for nice readable commit histories.
-
Does it make sense to try to install / maintain a gentoo system in a vm for learning more about Linux?
Gentoo could teach you more about what is involved in dependency handling and actual ‘construction’ of a Linux system. But Linux From Scratch is a much better teaching tool for learning this, and even things like Buildroot are arguably better than Gentoo for this because they generally force you to care about a lot of the stuff that Gentoo hides away to make the system nicer to use.
- Die Fahrplananzeiger der RNV laufen auf einem Raspberry Pi
riscv-gnu-toolchain
-
Is RISC-V ready for HPC? Evaluating the 64-core Sophon SG2042 RISC-V CPU
> no absurdely and grotesquely massive and complex compilers anywhere
Absence of evidence is not evidence of absence, and anyway there's not even an absence: https://github.com/riscv-collab/riscv-gnu-toolchain https://llvm.org/docs/RISCVUsage.html
> feature creeps on computer language syntax nowhere to be found
At least one of us is very confused, and in case it's me, how do language details matter to RISC-V?
-
Help trying to build for riscv64gc-unknown-linux-musl
I then looked at the .cargo/config.toml provided by the guide and saw that it wasn't actually statically compiling the code. After a bit of tinkering and building my own toolchain from here, I ended up with this config.toml file:
- GNU toolchain for RISC-V including GCC
-
Building a toolchain suitable for compiling V extension code
b) collabriscv - essentially gcc 12.2 + binutils master/2.40 as per https://github.com/riscv-collab/riscv-gnu-toolchain
- How do i specify vendor name while building the GNU toolchain?
-
GCC 13 Adds RISC-V T-Head Vendor Extension Collection
Or would it be better to take what is in https://github.com/riscv-collab/riscv-gnu-toolchain which is gcc 12.2 and start from there?
-
How to build toolchain with Zbs extension?
I'm not able to build https://github.com/riscv-collab/riscv-gnu-toolchain.git like this:
What are some alternatives?
rust-raspberrypi-OS-tutorials - :books: Learn to write an embedded OS in Rust :crab:
riscv-binutils-gdb - RISC-V backports for binutils-gdb. Development is done upstream at the FSF.
meta-balena - A collection of Yocto layers used to build balenaOS images
risc-v-examples - RISC-V examples for GD32V, K210, and QEMU
nerves - Platform infrastructure for embedded Erlang/OTP, Elixir, and LFE projects
rvv-llvm - This repository is outdated, support for RISC-V is now developed in upstream LLVM
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
freedom-tools - Tools for SiFive's Freedom Platform
linux-xlnx - The official Linux kernel from Xilinx
xv6-riscv - Xv6 for RISC-V
gokrazy - turn your Go program(s) into an appliance running on the Raspberry Pi 3, Pi 4, Pi Zero 2 W, or amd64 PCs!
riscv-gcc