muon
lfbb
Our great sponsors
| muon | lfbb | |
|---|---|---|
| 7 | 10 | |
| 2,828 | 56 | |
| - | - | |
| 0.0 | 6.2 | |
| about 1 year ago | about 1 month ago | |
| C | C++ | |
| MIT License | MIT License |
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.
muon
- This year in Servo: over 1000 pull requests and beyond
-
Muon: GPU Based Electron on a Diet
I do care, and in your example, it depends on what license the project uses and how "proprietary_library" is distributed.
In this specific case, Muon cannot be GPL'ed, for example, because it distributes a copy of Ultralight [1] and Ultralight has a proprietary (incompatible) license [2]. For a license like MIT or BSD, I think applying that license is technically valid, bug again, not very practical. I doubt Muon would make it into the OpenBSD repos, for example. Its distribution is hindered by the depedency.
[1] https://github.com/ImVexed/muon/tree/master/ultralight
[2] https://github.com/ultralight-ux/Ultralight/blob/master/lice...
- Muon - GPU Based Electron on a Diet
lfbb
- A lock-free ring-buffer with contiguous reservations (2019)
-
OpenPicoRTOS: 'cause the world DEFINITELY needs another RTOS !
If you're interested in how to do that you can check out a library of mine: https://github.com/DNedic/lfbb (although you don't need to bother with memory ordering if you don't want, you can just use the sequential consistency model).
-
How do you handle data coupling between RTOS tasks?
You might be interested to take a look at this if efficiency is one of your goals: https://github.com/DNedic/lfbb
-
Library for generic ringbuffer that can be filled via DMA?
I have exactly what you are looking for https://github.com/DNedic/lfbb
-
Best practices on loosely coupling the high-level modules on a sensor-packager-transmitter embedded c device.
I don't see a reason SensorCollector should send a flag when there is enough data to send, the circular buffer object should be able to tell you when there is enough data to send and it should not be coupled to your specific applicaton. For situations where you want the data to always be contigous and need a general purpose circular buffer, you can take a look at a library i wrote: https://github.com/DNedic/lfbb
- LFBB – A Lock Free Bipartite Buffer Library Written in Standard C11
-
Best practice for preventing data collisions between ISR and non ISR code without turning off interrupts? (FreeRTOS)
If you need something more advanced, check this out: https://github.com/DNedic/lfbb
- A Lock Free Bipartite Buffer Library Written in Standard C11
- Lock Free Bipartite Buffer Library Written in Standard C11
- A Lock Free Bipartite Buffer library written in standard C11
What are some alternatives?
libsamplerate - An audio Sample Rate Conversion library
lwrb - Lightweight generic ring buffer manager library
cmake-cookbook - CMake Cookbook recipes.
nanoprintf - The smallest public printf implementation for its feature set.
AppInitHook - Global user-mode hooking framework, based on AppInit_DLLs. The goal is to allow you to rapidly develop hooks to inject in an arbitrary process.
fifo_map - a FIFO-ordered associative container for C++
app_timer - Friendly, lightweight, hardware-agnostic timer abstraction layer in C. Use a single timer/counter source to drive many timed events.
Vitis-Tutorials - Vitis In-Depth Tutorials
Unity Test API - Simple Unit Testing for C
OpenPicoRTOS - Very small, safe, lightning fast, yet portable preemptive RTOS with SMP support
doctest - The fastest feature-rich C++11/14/17/20/23 single-header testing framework
fprime - F´ - A flight software and embedded systems framework