Yet Another Redis Library

Mirror of https://github.com/electric-sheep-co/yarl
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
Ryan Joseph e5b5947d51 List commands (phase one) il y a 1 an
azuresphere Update VS project to correctly reference yarl include path il y a 1 an
src List commands (phase one) il y a 1 an
test List commands (phase one) il y a 1 an
.gitignore Update .gitignore il y a 1 an
LICENSE Create LICENSE il y a 1 an
README.md Add KEYS, EXPIRE & EXPIREAT commands il y a 1 an

README.md

yarl

Yet Another Redis Library

A couple dev kits arrived that wanted for a POSIX C Redis library, so this is a port of arduino-redis into straight-C. Some day, that library will consume this one & morph into just a nice C++ facade.

Given the simple MCU platforms being targetted, a “bring your own file descriptor” interface seemed like it would do nicely. To that end, RedisConnection_t is typedefed simply to int, a.k.a. a file descriptor. It could be a socket FD, a pipe FD, even an actual file descriptor if you’re so inclined. Anything that can be read(2) from and write(2)-en to. BYOFD!

Building

The test app

Should build & run on any POSIX platform.

clang -o yarl_test  -Wall -Werror -I./src ./src/*.c ./test/test.c
  • add -DDEBUG=1 to generate debugging logging
  • add -O0 -g2 to disable optimizations and generate symbols, to enable debugging via lldb/gdb

The Azure Sphere library

Requires the Azure Sphere SDK (so also Windows & VS17 or VS19).

The VS project in the azuresphere directory is preconfigured to build a static library named libyarl.a in the standard build output location.

See this project for an example of consuming yarl as a build dependency.