efl/legacy/eet
Carsten Haitzler c127ff73e7 fix formatting
SVN revision: 50576
2010-07-28 03:03:10 +00:00
..
debian From: Mikhail Gusarov <dottedmag@dottedmag.net> 2009-08-17 01:31:38 +00:00
doc eet docs: next steps 2010-03-18 22:36:41 +00:00
m4 Add native Windows thread support instead of using pthread 2010-07-15 06:34:32 +00:00
src fix formatting 2010-07-28 03:03:10 +00:00
win32 * update Visual Studio project files 2010-04-03 05:29:44 +00:00
.cvsignore ignore++ 2008-06-19 12:30:57 +00:00
AUTHORS eet: mega doc update, still stuff to do. 2010-03-18 20:16:56 +00:00
COPYING fix the copying license to 2009-01-13 13:00:45 +00:00
COPYING-PLAIN add COPYING 2002-12-05 01:33:51 +00:00
ChangeLog * eet: reduce likeliness of race condition by checking file size too. 2010-07-20 16:13:51 +00:00
INSTALL minor fix of the doc about tests and coverage 2008-05-16 15:32:32 +00:00
Makefile.am Add native Windows thread support instead of using pthread 2010-07-15 06:34:32 +00:00
NEWS news has the release in it now. 2008-04-28 04:24:34 +00:00
README.in +E 2008-04-28 04:35:13 +00:00
autogen.sh add error checking to all autogen scripts 2005-08-03 01:00:21 +00:00
configure.ac Add native Windows thread support instead of using pthread 2010-07-15 06:34:32 +00:00
eet.pc.in Add native Windows thread support instead of using pthread 2010-07-15 06:34:32 +00:00
eet.spec.in After discussing with raster, this is what he requested for the spec 2010-04-18 07:03:09 +00:00

README.in

Eet @VERSION@

Requirements:
-------------
Must:
  libc libm zlib libjpeg
  Windows: evil

******************************************************************************
***
*** FOR ANY ISSUES WITH EET PLEASE EMAIL:
*** enlightenment-devel@lists.sourceforge.net
***
******************************************************************************

Eet is a tiny library designed to write an arbitary 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 arbitary files on the system. All
data is encoded in a platform independant way and can be written and
read by any architecture.

------------------------------------------------------------------------------
COMPILING AND INSTALLING:

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

------------------------------------------------------------------------------
BUILDING PACKAGES:

RPM: To build rpm packages:

  sudo rpm -ta @PACKAGE@-@VERSION@.tar.gz

You will find rpm packages in your system /usr/src/redhat/* dirs (note you may
not need to use sudo or root if you have your own ~/.rpmrc. see rpm documents
for more details)