eet - clean out old data from doc dir, set up for 1.4.0 release,
bring install in line with eina and move content to readme. readied for 1.4.0 alpha release. SVN revision: 51155
|
@ -1,47 +1,236 @@
|
||||||
COMPILING and INSTALLING:
|
Installation Instructions
|
||||||
|
*************************
|
||||||
|
|
||||||
If you got a official release tar archive do:
|
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
|
||||||
./configure
|
Software Foundation, Inc.
|
||||||
|
|
||||||
( otherwise if you got this from enlightenment cvs do: ./autogen.sh )
|
This file is free documentation; the Free Software Foundation gives
|
||||||
|
unlimited permission to copy, distribute and modify it.
|
||||||
|
|
||||||
Then to compile:
|
Basic Installation
|
||||||
make
|
==================
|
||||||
|
|
||||||
To install (run this as root, or the user who handles installs):
|
These are generic installation instructions.
|
||||||
make install
|
|
||||||
|
|
||||||
To run the unit tests (See Note 5 below):
|
The `configure' shell script attempts to guess correct values for
|
||||||
make check
|
various system-dependent variables used during compilation. It uses
|
||||||
|
those values to create a `Makefile' in each directory of the package.
|
||||||
|
It may also create one or more `.h' files containing system-dependent
|
||||||
|
definitions. Finally, it creates a shell script `config.status' that
|
||||||
|
you can run in the future to recreate the current configuration, and a
|
||||||
|
file `config.log' containing compiler output (useful mainly for
|
||||||
|
debugging `configure').
|
||||||
|
|
||||||
To get the coverage report (See Notes 6 and 7 below):
|
It can also use an optional file (typically called `config.cache'
|
||||||
make coverage
|
and enabled with `--cache-file=config.cache' or simply `-C') that saves
|
||||||
|
the results of its tests to speed up reconfiguring. (Caching is
|
||||||
|
disabled by default to prevent problems with accidental use of stale
|
||||||
|
cache files.)
|
||||||
|
|
||||||
The report is created in the coverage/ subdir
|
If you need to do unusual things to compile the package, please try
|
||||||
|
to figure out how `configure' could check whether to do them, and mail
|
||||||
|
diffs or instructions to the address given in the `README' so they can
|
||||||
|
be considered for the next release. If you are using the cache, and at
|
||||||
|
some point `config.cache' contains results you don't want to keep, you
|
||||||
|
may remove or edit it.
|
||||||
|
|
||||||
|
The file `configure.ac' (or `configure.in') is used to create
|
||||||
|
`configure' by a program called `autoconf'. You only need
|
||||||
|
`configure.ac' if you want to change it or regenerate `configure' using
|
||||||
|
a newer version of `autoconf'.
|
||||||
|
|
||||||
|
The simplest way to compile this package is:
|
||||||
|
|
||||||
|
1. `cd' to the directory containing the package's source code and type
|
||||||
|
`./configure' to configure the package for your system. If you're
|
||||||
|
using `csh' on an old version of System V, you might need to type
|
||||||
|
`sh ./configure' instead to prevent `csh' from trying to execute
|
||||||
|
`configure' itself.
|
||||||
|
|
||||||
NOTE 1: You MUST make install Eet for it to run properly.
|
Running `configure' takes awhile. While running, it prints some
|
||||||
|
messages telling which features it is checking for.
|
||||||
|
|
||||||
NOTE 2: For compilation with MinGW, fnmatch.h is probably missing.
|
2. Type `make' to compile the package.
|
||||||
That file can be found here:
|
|
||||||
http://www.koders.com/c/fid2B518462CB1EED3D4E31E271DB83CD1582F6EEBE.aspx
|
|
||||||
It should be installed in the mingw include directory.
|
|
||||||
|
|
||||||
NOTE 3: For compilation with mingw32ce, run configure with the option
|
3. Optionally, type `make check' to run any self-tests that come with
|
||||||
|
the package.
|
||||||
|
|
||||||
--host=arm-wince-mingw32ce
|
4. Type `make install' to install the programs and any data files and
|
||||||
|
documentation.
|
||||||
|
|
||||||
NOTE 4: For compilation with cegcc, follow the wiki:
|
5. You can remove the program binaries and object files from the
|
||||||
|
source code directory by typing `make clean'. To also remove the
|
||||||
|
files that `configure' created (so you can compile the package for
|
||||||
|
a different kind of computer), type `make distclean'. There is
|
||||||
|
also a `make maintainer-clean' target, but that is intended mainly
|
||||||
|
for the package's developers. If you use it, you may have to get
|
||||||
|
all sorts of other programs in order to regenerate files that came
|
||||||
|
with the distribution.
|
||||||
|
|
||||||
http://wiki.enlightenment.org/index.php/Category:EFL_Windows_CE
|
Compilers and Options
|
||||||
|
=====================
|
||||||
|
|
||||||
NOTE 5: If you want to be able to run make check, you need library check
|
Some systems require unusual options for compilation or linking that the
|
||||||
from http://check.sourceforge.net/.
|
`configure' script does not know about. Run `./configure --help' for
|
||||||
|
details on some of the pertinent environment variables.
|
||||||
|
|
||||||
NOTE 6: If you want to be able to run coverage test over eet, you will need
|
You can give `configure' initial values for configuration parameters
|
||||||
gcov (usually any distro provides it) and lcov from
|
by setting variables in the command line or in the environment. Here
|
||||||
http://ltp.sourceforge.net/coverage/lcov.php.
|
is an example:
|
||||||
|
|
||||||
|
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
|
||||||
|
|
||||||
|
*Note Defining Variables::, for more details.
|
||||||
|
|
||||||
|
Compiling For Multiple Architectures
|
||||||
|
====================================
|
||||||
|
|
||||||
|
You can compile the package for more than one kind of computer at the
|
||||||
|
same time, by placing the object files for each architecture in their
|
||||||
|
own directory. To do this, you must use a version of `make' that
|
||||||
|
supports the `VPATH' variable, such as GNU `make'. `cd' to the
|
||||||
|
directory where you want the object files and executables to go and run
|
||||||
|
the `configure' script. `configure' automatically checks for the
|
||||||
|
source code in the directory that `configure' is in and in `..'.
|
||||||
|
|
||||||
|
If you have to use a `make' that does not support the `VPATH'
|
||||||
|
variable, you have to compile the package for one architecture at a
|
||||||
|
time in the source code directory. After you have installed the
|
||||||
|
package for one architecture, use `make distclean' before reconfiguring
|
||||||
|
for another architecture.
|
||||||
|
|
||||||
|
Installation Names
|
||||||
|
==================
|
||||||
|
|
||||||
|
By default, `make install' installs the package's commands under
|
||||||
|
`/usr/local/bin', include files under `/usr/local/include', etc. You
|
||||||
|
can specify an installation prefix other than `/usr/local' by giving
|
||||||
|
`configure' the option `--prefix=PREFIX'.
|
||||||
|
|
||||||
|
You can specify separate installation prefixes for
|
||||||
|
architecture-specific files and architecture-independent files. If you
|
||||||
|
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
|
||||||
|
PREFIX as the prefix for installing programs and libraries.
|
||||||
|
Documentation and other data files still use the regular prefix.
|
||||||
|
|
||||||
|
In addition, if you use an unusual directory layout you can give
|
||||||
|
options like `--bindir=DIR' to specify different values for particular
|
||||||
|
kinds of files. Run `configure --help' for a list of the directories
|
||||||
|
you can set and what kinds of files go in them.
|
||||||
|
|
||||||
|
If the package supports it, you can cause programs to be installed
|
||||||
|
with an extra prefix or suffix on their names by giving `configure' the
|
||||||
|
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
|
||||||
|
|
||||||
|
Optional Features
|
||||||
|
=================
|
||||||
|
|
||||||
|
Some packages pay attention to `--enable-FEATURE' options to
|
||||||
|
`configure', where FEATURE indicates an optional part of the package.
|
||||||
|
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
|
||||||
|
is something like `gnu-as' or `x' (for the X Window System). The
|
||||||
|
`README' should mention any `--enable-' and `--with-' options that the
|
||||||
|
package recognizes.
|
||||||
|
|
||||||
|
For packages that use the X Window System, `configure' can usually
|
||||||
|
find the X include and library files automatically, but if it doesn't,
|
||||||
|
you can use the `configure' options `--x-includes=DIR' and
|
||||||
|
`--x-libraries=DIR' to specify their locations.
|
||||||
|
|
||||||
|
Specifying the System Type
|
||||||
|
==========================
|
||||||
|
|
||||||
|
There may be some features `configure' cannot figure out automatically,
|
||||||
|
but needs to determine by the type of machine the package will run on.
|
||||||
|
Usually, assuming the package is built to be run on the _same_
|
||||||
|
architectures, `configure' can figure that out, but if it prints a
|
||||||
|
message saying it cannot guess the machine type, give it the
|
||||||
|
`--build=TYPE' option. TYPE can either be a short name for the system
|
||||||
|
type, such as `sun4', or a canonical name which has the form:
|
||||||
|
|
||||||
|
CPU-COMPANY-SYSTEM
|
||||||
|
|
||||||
|
where SYSTEM can have one of these forms:
|
||||||
|
|
||||||
|
OS KERNEL-OS
|
||||||
|
|
||||||
|
See the file `config.sub' for the possible values of each field. If
|
||||||
|
`config.sub' isn't included in this package, then this package doesn't
|
||||||
|
need to know the machine type.
|
||||||
|
|
||||||
|
If you are _building_ compiler tools for cross-compiling, you should
|
||||||
|
use the option `--target=TYPE' to select the type of system they will
|
||||||
|
produce code for.
|
||||||
|
|
||||||
|
If you want to _use_ a cross compiler, that generates code for a
|
||||||
|
platform different from the build platform, you should specify the
|
||||||
|
"host" platform (i.e., that on which the generated programs will
|
||||||
|
eventually be run) with `--host=TYPE'.
|
||||||
|
|
||||||
|
Sharing Defaults
|
||||||
|
================
|
||||||
|
|
||||||
|
If you want to set default values for `configure' scripts to share, you
|
||||||
|
can create a site shell script called `config.site' that gives default
|
||||||
|
values for variables like `CC', `cache_file', and `prefix'.
|
||||||
|
`configure' looks for `PREFIX/share/config.site' if it exists, then
|
||||||
|
`PREFIX/etc/config.site' if it exists. Or, you can set the
|
||||||
|
`CONFIG_SITE' environment variable to the location of the site script.
|
||||||
|
A warning: not all `configure' scripts look for a site script.
|
||||||
|
|
||||||
|
Defining Variables
|
||||||
|
==================
|
||||||
|
|
||||||
|
Variables not defined in a site shell script can be set in the
|
||||||
|
environment passed to `configure'. However, some packages may run
|
||||||
|
configure again during the build, and the customized values of these
|
||||||
|
variables may be lost. In order to avoid this problem, you should set
|
||||||
|
them in the `configure' command line, using `VAR=value'. For example:
|
||||||
|
|
||||||
|
./configure CC=/usr/local2/bin/gcc
|
||||||
|
|
||||||
|
causes the specified `gcc' to be used as the C compiler (unless it is
|
||||||
|
overridden in the site shell script). Here is a another example:
|
||||||
|
|
||||||
|
/bin/bash ./configure CONFIG_SHELL=/bin/bash
|
||||||
|
|
||||||
|
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
|
||||||
|
configuration-related scripts to be executed by `/bin/bash'.
|
||||||
|
|
||||||
|
`configure' Invocation
|
||||||
|
======================
|
||||||
|
|
||||||
|
`configure' recognizes the following options to control how it operates.
|
||||||
|
|
||||||
|
`--help'
|
||||||
|
`-h'
|
||||||
|
Print a summary of the options to `configure', and exit.
|
||||||
|
|
||||||
|
`--version'
|
||||||
|
`-V'
|
||||||
|
Print the version of Autoconf used to generate the `configure'
|
||||||
|
script, and exit.
|
||||||
|
|
||||||
|
`--cache-file=FILE'
|
||||||
|
Enable the cache: use and save the results of the tests in FILE,
|
||||||
|
traditionally `config.cache'. FILE defaults to `/dev/null' to
|
||||||
|
disable caching.
|
||||||
|
|
||||||
|
`--config-cache'
|
||||||
|
`-C'
|
||||||
|
Alias for `--cache-file=config.cache'.
|
||||||
|
|
||||||
|
`--quiet'
|
||||||
|
`--silent'
|
||||||
|
`-q'
|
||||||
|
Do not print messages saying which checks are being made. To
|
||||||
|
suppress all normal output, redirect it to `/dev/null' (any error
|
||||||
|
messages will still be shown).
|
||||||
|
|
||||||
|
`--srcdir=DIR'
|
||||||
|
Look for the package's source code in directory DIR. Usually
|
||||||
|
`configure' can determine that directory automatically.
|
||||||
|
|
||||||
|
`configure' also accepts some other, not widely useful, options. Run
|
||||||
|
`configure --help' for more details.
|
||||||
|
|
||||||
NOTE 7: For coverage support you also need check support.
|
|
||||||
|
|
|
@ -1,17 +1,25 @@
|
||||||
Eet @VERSION@
|
Eet @VERSION@ ALPHA
|
||||||
|
|
||||||
|
******************************************************************************
|
||||||
|
|
||||||
|
FOR ANY ISSUES PLEASE EMAIL:
|
||||||
|
enlightenment-devel@lists.sourceforge.net
|
||||||
|
|
||||||
|
******************************************************************************
|
||||||
|
|
||||||
Requirements:
|
Requirements:
|
||||||
-------------
|
-------------
|
||||||
Must:
|
Must have:
|
||||||
libc libm zlib libjpeg
|
libc
|
||||||
Windows: evil
|
libm
|
||||||
|
zlib
|
||||||
|
libjpeg
|
||||||
|
eina (1.0.0 or better)
|
||||||
|
(For windows you also need: evil)
|
||||||
|
|
||||||
******************************************************************************
|
Optional requirements:
|
||||||
***
|
gnutls (1.7.6 or better)
|
||||||
*** FOR ANY ISSUES WITH EET PLEASE EMAIL:
|
openssl
|
||||||
*** enlightenment-devel@lists.sourceforge.net
|
|
||||||
***
|
|
||||||
******************************************************************************
|
|
||||||
|
|
||||||
Eet is a tiny library designed to write an arbitary set of chunks of
|
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
|
data to a file and optionally compress each chunk (very much like a
|
||||||
|
@ -23,7 +31,10 @@ 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
|
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
|
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
|
data is encoded in a platform independant way and can be written and
|
||||||
read by any architecture.
|
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).
|
||||||
|
|
||||||
------------------------------------------------------------------------------
|
------------------------------------------------------------------------------
|
||||||
COMPILING AND INSTALLING:
|
COMPILING AND INSTALLING:
|
||||||
|
@ -33,13 +44,26 @@ COMPILING AND INSTALLING:
|
||||||
(do this as root unless you are installing in your users directories):
|
(do this as root unless you are installing in your users directories):
|
||||||
make install
|
make install
|
||||||
|
|
||||||
------------------------------------------------------------------------------
|
To get the coverage report:
|
||||||
BUILDING PACKAGES:
|
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:
|
||||||
|
http://ltp.sourceforge.net/coverage/lcov.php.
|
||||||
|
For coverage support you also need "make check" support with the check
|
||||||
|
library (see below).
|
||||||
|
|
||||||
RPM: To build rpm packages:
|
For compilation with MinGW, fnmatch.h is probably missing. That file can be
|
||||||
|
found here:
|
||||||
|
http://www.koders.com/c/fid2B518462CB1EED3D4E31E271DB83CD1582F6EEBE.aspx
|
||||||
|
It should be installed in the mingw include directory.
|
||||||
|
|
||||||
sudo rpm -ta @PACKAGE@-@VERSION@.tar.gz
|
For compilation with mingw32ce, run configure with the option
|
||||||
|
--host=arm-wince-mingw32ce
|
||||||
|
|
||||||
|
For compilation with cegcc, follow the wiki:
|
||||||
|
http://wiki.enlightenment.org/index.php/Category:EFL_Windows_CE
|
||||||
|
|
||||||
|
If you want to be able to run "make check", you need library check
|
||||||
|
from http://check.sourceforge.net/
|
||||||
|
|
||||||
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)
|
|
||||||
|
|
|
@ -1,12 +1,12 @@
|
||||||
##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
|
##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
|
||||||
##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
|
##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
|
||||||
m4_define([v_maj], [1])
|
m4_define([v_maj], [1])
|
||||||
m4_define([v_min], [3])
|
m4_define([v_min], [4])
|
||||||
m4_define([v_mic], [3])
|
m4_define([v_mic], [0])
|
||||||
m4_define([v_rev], m4_esyscmd([(svnversion "${SVN_REPO_PATH:-.}" | grep -v export || echo 0) | awk -F : '{printf("%s\n", $1);}' | tr -d ' :MSP\n']))
|
m4_define([v_rev], m4_esyscmd([(svnversion "${SVN_REPO_PATH:-.}" | grep -v export || echo 0) | awk -F : '{printf("%s\n", $1);}' | tr -d ' :MSP\n']))
|
||||||
m4_if(v_rev, [0], [m4_define([v_rev], m4_esyscmd([git log 2> /dev/null | (grep -m1 git-svn-id || echo 0) | sed -e 's/.*@\([0-9]*\).*/\1/' | tr -d '\n']))])
|
m4_if(v_rev, [0], [m4_define([v_rev], m4_esyscmd([git log 2> /dev/null | (grep -m1 git-svn-id || echo 0) | sed -e 's/.*@\([0-9]*\).*/\1/' | tr -d '\n']))])
|
||||||
##-- When released, remove the dnl on the below line
|
##-- When released, remove the dnl on the below line
|
||||||
dnl m4_undefine([v_rev])
|
m4_undefine([v_rev])
|
||||||
##-- When doing snapshots - change soname. remove dnl on below line
|
##-- When doing snapshots - change soname. remove dnl on below line
|
||||||
dnl m4_define([relname], [ver-pre-svn-05])
|
dnl m4_define([relname], [ver-pre-svn-05])
|
||||||
dnl m4_define([v_rel], [-release relname])
|
dnl m4_define([v_rel], [-release relname])
|
||||||
|
@ -18,7 +18,7 @@ m4_define([lt_age], v_min)
|
||||||
##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
|
##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
|
||||||
##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
|
##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
|
||||||
|
|
||||||
AC_INIT([eet], [v_ver], [enlightenment-devel@lists.sourceforge.net])
|
AC_INIT([eet], [v_ver-alpha], [enlightenment-devel@lists.sourceforge.net])
|
||||||
AC_PREREQ([2.52])
|
AC_PREREQ([2.52])
|
||||||
AC_CONFIG_SRCDIR([configure.ac])
|
AC_CONFIG_SRCDIR([configure.ac])
|
||||||
AC_CONFIG_MACRO_DIR([m4])
|
AC_CONFIG_MACRO_DIR([m4])
|
||||||
|
@ -253,8 +253,8 @@ AC_SUBST(EET_LIBS)
|
||||||
|
|
||||||
# Eina library
|
# Eina library
|
||||||
|
|
||||||
PKG_CHECK_MODULES(EINA, [eina-0])
|
PKG_CHECK_MODULES(EINA, [eina-1])
|
||||||
requirement_eet="eina-0 ${requirement_eet}"
|
requirement_eet="eina-1 >= 1.0.0 ${requirement_eet}"
|
||||||
|
|
||||||
# Gnutls library
|
# Gnutls library
|
||||||
have_gnutls="no"
|
have_gnutls="no"
|
||||||
|
|
Before Width: | Height: | Size: 266 B |
Before Width: | Height: | Size: 39 KiB |
Before Width: | Height: | Size: 915 KiB |
Before Width: | Height: | Size: 753 B |
Before Width: | Height: | Size: 3.7 KiB |
Before Width: | Height: | Size: 73 KiB |
Before Width: | Height: | Size: 915 KiB |
Before Width: | Height: | Size: 753 B |
Before Width: | Height: | Size: 3.7 KiB |
Before Width: | Height: | Size: 73 KiB |
Before Width: | Height: | Size: 915 KiB |
Before Width: | Height: | Size: 753 B |
Before Width: | Height: | Size: 3.7 KiB |
Before Width: | Height: | Size: 1.7 KiB |
Before Width: | Height: | Size: 2.0 KiB |
Before Width: | Height: | Size: 979 B |
Before Width: | Height: | Size: 317 B |
Before Width: | Height: | Size: 72 KiB |
Before Width: | Height: | Size: 86 KiB |
|
@ -44,7 +44,7 @@ extern "C" {
|
||||||
*/
|
*/
|
||||||
|
|
||||||
#define EET_VERSION_MAJOR 1
|
#define EET_VERSION_MAJOR 1
|
||||||
#define EET_VERSION_MINOR 3
|
#define EET_VERSION_MINOR 4
|
||||||
/**
|
/**
|
||||||
* @typedef Eet_Version
|
* @typedef Eet_Version
|
||||||
*
|
*
|
||||||
|
|