Menu

Tree [dfc1b9] master /
 History

HTTPS access


File Date Author Commit
 doc 2014-11-23 Alexander Vdolainen Alexander Vdolainen [030129] initial commit
 examples 2014-11-23 Alexander Vdolainen Alexander Vdolainen [030129] initial commit
 include 2019-05-21 Alexander Vdolainen Alexander Vdolainen [dfc1b9] Changes below:
 lib 2019-05-21 Alexander Vdolainen Alexander Vdolainen [700723] Code style compliance;
 man 2019-05-21 Alexander Vdolainen Alexander Vdolainen [dfc1b9] Changes below:
 tests 2019-05-12 Alexander Vdolainen Alexander Vdolainen [bb6a20] Few things --- there are:
 .gitignore 2019-04-25 Alexander Vdolainen Alexander Vdolainen [459ca3] INSTALL is not a part of source tree;
 AUTHORS 2019-04-25 Alexander Vdolainen Alexander Vdolainen [54cdc0] I fought my laziness: names are in place;
 COPYING 2018-06-11 Alexander Vdolainen Alexander Vdolainen [e5f878] LGPLv2.1 reverted; Autotools update; CAS added;
 ChangeLog 2018-11-14 Alexander Vdolainen Alexander Vdolainen [506b08] Autotools build fix;
 Makefile.am 2019-05-21 Alexander Vdolainen Alexander Vdolainen [dfc1b9] Changes below:
 NEWS 2015-12-26 Alexander Vdolainen Alexander Vdolainen [062c7f] NEWS updates;
 README 2019-04-25 Alexander Vdolainen Alexander Vdolainen [1329e7] README updated;
 VERSION 2019-05-21 Alexander Vdolainen Alexander Vdolainen [5a60ed] Version number increase;
 autogen.sh 2018-06-11 Alexander Vdolainen Alexander Vdolainen [e5f878] LGPLv2.1 reverted; Autotools update; CAS added;
 configure.ac 2019-05-21 Alexander Vdolainen Alexander Vdolainen [dfc1b9] Changes below:

Read Me

1. What is that ?
this is a small C library with a collection of small useful stuff such as:
 * Index allocator
 * Linked list implementation, looks like a linux kernel one
 * Collection of the binary search tree implementation:
   * Btree
   * AVL
   * Red black
   * Splay

2. Is it useful ?
I hope so, usually I have a lot of tools or applications are required 
to use index allocation, or some kind of structures to search within.
I guess it might be useful for everybody who looks the same thing (implementing
the same boring stuff each time isn't productive).

3. Is it stable ?
Yes, it is stable. But if you will find a bug, please report me via email.
Actually it's used a lot (mostly in some firmware images and in my own pet 
projects as well). 

4. How to build ?

4.1. Simple way:
Just type ./autogen.sh, and you will have a configure script with a 
common autotools options (e.g. make && make install).

4.2. Proper way:
 - Create directory outside of the code tree, let's say libtdata-build
 - Do ./autogen.sh within source tree
 - Go to your 'libtdata-build' directory
 - ./configure && make && make install (don't forget sudo for install target)

4.3. Configure options:
At the moment just the standard options are exist, so more valuable is
--prefix=<installation prefix>

5. Are there new features coming ?
Yep, something is coming. I'm planning to implement CTries (just for fun).

6. Contact
Currently this library is maintained by avdolainen at zoho dot com.
To post bugs, requests, questions you may use sf.net: http://libtdata.sf.net