Embedded Linux для начинающих (Часть первая)
Однажды по работе мне прилетела задача по сборке и запуску Linux на одноплатном ПК. Тогда я, будучи разработчиком ПО для микроконтроллеров, встал в небольшой ступор — задачка явно не решалась установкой IDE и нажатием в ней кнопки «Собрать проект». Гугл помог узнать о том, что существует некий Buildroot. В материалах по теме всё выглядело довольно просто: скачай, настрой, дерни пару команд, загрузи результат на одноплатник — и можно запускать! Получается, процесс не многим сложнее установки дистрибутива Linux или Windows на обычный ПК? Конечно же, нет. Ведь если у тебя в руках кастомный одноплатник неизвестного китайского бренда, а не BeagleBone или Raspberry Pi, то зарыться в Buildroot придётся с головой...
#pkgconfig's rules about when it does or does not apply a sysroot base seem to be very inconsistent. I guess I'm going to have to look at the actual code to see why this may be. #crosscompiling #buildroot
@dey For me #buildroot is a great way to build reproducible images with all the config files in a git repo. We build images for dozens of different devices that receive regular updates over the air, works great!
Il y a des gens qui bidouillent avec buildroot?
Certes c'est facile pour produire une image pour le raspberry hyper simple, mais pour la suite, ça devient tendu…
Franchement respect pour votre courage.
Even the #buildroot Mailinglist isn‘t safe from AI-„Improvements“ anymore 
The Oregon State University's Open Source Lab needs your help 
!
We at #Inkscape rely on them for hosting our website 
, mailing lists 
, mail servers 
and DNS 
.
They are also a host for many other open source projects - e.g. #Drupal, #Gentoo Linux, #Debian, #Fedora, #phpBB, #OpenID, #Buildroot/#Busybox, #Cinc, …
Please consider donating 
to them so they can keep their services running for all of us!
Heads up for anyone planning to set up a Buildroot environment on the newly released Fedora 42 @fedora
I have just submitted a patch for the m4 package to address compatibility with GCC 15. If you're working with Buildroot on this release, you may want to review the patch details here:
https://lists.buildroot.org/pipermail/buildroot/2025-April/777274.html
How to build and configure a custom Linux image for the Raspberry Pi 5 using Buildroot.
“This process not only gives you a deeper understanding of embedded systems, but also provides you with a powerful, customizable environment tailored to your needs.”
https://dev.to/pfs/custom-linux-image-for-raspberry-pi-5-a-guide-with-buildroot-bp3
#buildroot #raspberrypi #linux #embedded #pios #debian #pixel #lxqt 14673889
@lawik a friend said it best, it’s like the SAP or Oracle of the embedded Linux world. It’s just plain terrible.
If you ever end up in a situation where someone asks, How about Yocto? You skuld just walk out of the room.
Call me, or anyone else really working with #buildroot, instead. Your life will be much better, sleep improves, your loved ones will smile at you again. Sure, you may not make as much money, but you can see that as an investment in your sanity and happiness.
I may be biased, having seen the light that is #buildroot, but I really hate Yocto! 
can’t wait to get off this assignment.
https://www.ott.net/buildroot-initramfs/ - new post on how to use #buildroot to build a custom #initramfs
So, needless to say, I’ve started looking around for other opportunities. Even an early pension.
CV: I’m OK at Linux and UNIX systems. I have a few hobby projects that are #OpenSource and I’d like to work with #buildroot based systems if possible. #FediHire #Sweden
#Python package management question: Is there some way to have pip (and tools using it, e.g. Nox/Tox) to use local sources and ideally distro installs, and only download from PyPI after explicit confirmation? I'm well aware of venv etc., my point is about the pip calls to set those up.
Ideally, what I'd want pip to do to resolve a package, in order:
1. Check a list of locally configured source directories. As in, if I have the repository for package A, I add that directory to a list/mapping, and then A always gets installed from the source as present there, or a specific tag.
2. Use the package as installed by my distro. This is similar to pipx install --system-site-packages, but I'd only want the explicitly installed packages available in the venv (or pipx install, etc.), not all, so tests can confirm that the dependencies listed in pyproject.toml are actually complete.
3. Use a local cache of PyPI (and optionally other sources) packages.
4. Fetch to/update cache only after explicit approval.index-url or find-links don't cover this, because they require pre-built sdist/wheel packages. I want to be able to work offline as far as possible, and keep track of the exact sources I'm using. Partially inspired by #Buildroot, which gives me an archive of all sources used in my firmware build as part of the concept.
As far as I see it now, if I really want this without heavily patching pip, my only option would be to implement all this as something that provides a web interface I can use as index-url, and I'm not excited about that idea. 
Happy I Love Free Software Day 
#ilovefs #softwarefreedom #foss #opensource @kirschner
Some of my favorite projects and organizations that contribute to #freesoftware (in no particular order):
@fedora
@opensuse
@debian
@tails
@signalapp
@homeassistant
@nextcloud
@icing
@raspberrypi @linuxfoundation
@conservancy
@matrix
@fsfe
@ThePSF
@sovtechfund
@iscdotorg
#Linux
#systemd
#buildroot
#fediverse
...
Thank you to everyone who dedicates their time to contribute to open source software
The January #Buildroot updates are out, with 2024.11.1 for our current release and 2024.02.10 for the LTS. The next release will be 2025.02, which will become the new LTS. https://lore.kernel.org/buildroot/87y0zkhumg.fsf@dell.be.48ers.dk/T/#u https://lore.kernel.org/buildroot/8734hsjdak.fsf@dell.be.48ers.dk/T/#u
- Two #DOjS releases and a #win32 port
- A new release of #jSH
- Contributed #DJGPP patches to #mbedTLS and #jasper
- Updated my #BuildRoot GeodeLX repo
- Updated DOSQLite (#SQLite for MS-DOS)
- 11 Updates to #DOStodon (#MastodonClient for MS-DOS)
The process of taking my developer #buildroot image filled with useful utilities to a minimal test case for one package (#vkmark) is certainly giving my processor a work out today. I may not need to turn on the office heater....
