3 ms·
Two issues with readline: it's GPL and it's big. For embedded systems intended to become products you really need something else. My tiny variant is this, but
by jhallenworld 4y ago
Two issues with readline: it's GPL and it's big. For embedded systems intended to become products you really need something else. My tiny variant is this, but for sure there are many others:
https://github.com/nklabs/libnklabs https://github.com/nklabs/libnklabs
("nkreadline" has editing, tab-completion (for embedded "nkcli" commands) and history)
- trelane 4y agoFor me as a customer, the GPL is a feature, not an "issue." Of course, if you ship software for your hardware and want to lock your customers out of their own hardware, then I can see why you'd not choose it.
- jhallenworld 4y agoI don't disagree with you (I've written plenty of GPL-licensed software), but as someone who gets paid to develop products for other companies, it's an issue. Few of my customers are interested in making the embedded software for their product open source. Actually the MIT open source license (and other similar ones) solves a completely different problem for me. It allows me to reuse this software for many different customers. It's slightly easier to do this when I tell them that I'm going to use "this open source library" vs. "my personal library that I'm granting you a license for this product, but I retain the right to use it for other customers".