https://buildroot.org/ is a popular framework for generating embedded Linux systems. It ships with a bunch of packages. One of them is fluent-bit, which I recently added for a colleague to buildroot.
I have four questions related to the fluent-bit package in buildroot:
1. Bump c-ares & xxhash:
Is it possible to bump c-ares & xxhash (lib/cfl) to the latest nightly versions, or add these two patches for the time being?:
2. Linking against shared libraries.
Related to this mail: https://lists.buildroot.org/pipermail/buildroot/2023-February/662141.html, is it an idea to make it possible to link against already installed libraries on the system? For E.g. c-ares is a buildroot package, so if CMake does a quick check (pkg-config), the (re-)compilation could be omitted.
3. Use buildroot to test e.g. glibc, uclibc, musl.
Consider using buildroot to test against multiple systems to avoid any regression.
This will compile fluent-bit for a wide variety of architectures and toolchains.
$ git clone https://github.com/buildroot/buildroot.git
$ cd buildroot/
$ ./utils/test-pkg -p fluent-bit -a
4. Consider sending buildroot bumps.
It would be appreciated if bump patches are upstreamed towards buildroot. By this, all buildroot devs could quickly get access to the latest and greatest.
https://buildroot.org/ is a popular framework for generating embedded Linux systems. It ships with a bunch of packages. One of them is fluent-bit, which I recently added for a colleague to buildroot.
I have four questions related to the fluent-bit package in buildroot:
1. Bump c-ares & xxhash:
Is it possible to bump c-ares & xxhash (lib/cfl) to the latest nightly versions, or add these two patches for the time being?:
2. Linking against shared libraries.
Related to this mail: https://lists.buildroot.org/pipermail/buildroot/2023-February/662141.html, is it an idea to make it possible to link against already installed libraries on the system? For E.g. c-ares is a buildroot package, so if CMake does a quick check (pkg-config), the (re-)compilation could be omitted.
3. Use buildroot to test e.g. glibc, uclibc, musl.
Consider using buildroot to test against multiple systems to avoid any regression.
This will compile fluent-bit for a wide variety of architectures and toolchains.
$ git clone https://github.com/buildroot/buildroot.git $ cd buildroot/ $ ./utils/test-pkg -p fluent-bit -a4. Consider sending buildroot bumps.
It would be appreciated if bump patches are upstreamed towards buildroot. By this, all buildroot devs could quickly get access to the latest and greatest.