You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Cedric BAIL 41dd379872 eet: reduce the time taken by eet tests suite and hopefully reduce the risk for failure. 12 years ago
doc fix paths to be relative to project build root. 12 years ago
m4 eet: use eina_lock. 13 years ago
src eet: reduce the time taken by eet tests suite and hopefully reduce the risk for failure. 12 years ago
.gitignore Add ignore and update files 12 years ago
AUTHORS change of email address: this is going to be ugly 12 years ago
COPYING fix COPYING to say 2011. 12 years ago
ChangeLog eet: write to standard output if no output file given. 12 years ago
INSTALL eet - clean out old data from doc dir, set up for 1.4.0 release, 13 years ago buildbot: new attempt at coverage support. 12 years ago
NEWS unrevert 65828 and unspank myself. 12 years ago
README update READMe for eet 12 years ago Ticket #824 - no's 12 years ago eet: Fixed svn detection for svn1.7 12 years ago no more dependency on pthread 12 years ago Minor adjustments to the current status. 12 years ago


Eet 1.1.0




Must have:
eina (1.1.0 or better)
(For windows you also need: evil)

Optional requirements:
gnutls (1.7.6 or better)

Eet is a tiny library designed to write an arbitrary set of chunks of
data to a file and optionally compress each chunk (very much like a
zip file) and allow fast random-access reading of the file later
on. It does not do zip as a zip itself has more complexity than is
needed, and it was much simpler to implement this once here.

It also can encode and decode data structures in memory, as well as
image data for saving to eet files or sending across the network to
other machines, or just writing to arbitrary files on the system. All
data is encoded in a platform independent way and can be written and
read by any architecture. This data once encoded can be sent to
another process or machine and decoded on the other end without
needing to go into an eet file. Eet can also optionally encrypt files
and use digital signatures (with gnutls or openssl support).


(do this as root unless you are installing in your users directories):
make install

To get the coverage report:
make coverage
The report is created in the coverage/ subdir
If you want to be able to run coverage test over eet, you will need gcov
(usually any distro provides it) and lcov from:
For coverage support you also need "make check" support with the check
library (see below).

For compilation with MinGW, fnmatch.h is probably missing. That file can be
found here:
It should be installed in the mingw include directory.

For compilation with mingw32ce, run configure with the option

For compilation with cegcc, follow the wiki:

If you want to be able to run "make check", you need library check