summaryrefslogtreecommitdiff
path: root/legacy
diff options
context:
space:
mode:
authorCarsten Haitzler <raster@rasterman.com>2010-08-16 09:59:13 +0000
committerCarsten Haitzler <raster@rasterman.com>2010-08-16 09:59:13 +0000
commit2bc24a316fb66632e171e44ad9b398b53c844c71 (patch)
tree6dd59697c5a5c890fe387b633ddb329b24951593 /legacy
parent1a979c596c7ec8de525fdfdf38b19da70cf0ead2 (diff)
eeze - 1.0.0 alpha ready.
SVN revision: 51185
Diffstat (limited to 'legacy')
-rw-r--r--legacy/eeze/INSTALL156
-rw-r--r--legacy/eeze/README29
-rw-r--r--legacy/eeze/configure.ac15
-rw-r--r--legacy/eeze/src/lib/Eeze.h24
4 files changed, 91 insertions, 133 deletions
diff --git a/legacy/eeze/INSTALL b/legacy/eeze/INSTALL
index 2550dab752..23e5f25d0e 100644
--- a/legacy/eeze/INSTALL
+++ b/legacy/eeze/INSTALL
@@ -1,19 +1,16 @@
1Installation Instructions 1Installation Instructions
2************************* 2*************************
3 3
4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, 4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
52006, 2007, 2008, 2009 Free Software Foundation, Inc. 5Software Foundation, Inc.
6 6
7 This file is free documentation; the Free Software Foundation gives 7This file is free documentation; the Free Software Foundation gives
8unlimited permission to copy, distribute and modify it. 8unlimited permission to copy, distribute and modify it.
9 9
10Basic Installation 10Basic Installation
11================== 11==================
12 12
13 Briefly, the shell commands `./configure; make; make install' should 13These are generic installation instructions.
14configure, build, and install this package. The following
15more-detailed instructions are generic; see the `README' file for
16instructions specific to this package.
17 14
18 The `configure' shell script attempts to guess correct values for 15 The `configure' shell script attempts to guess correct values for
19various system-dependent variables used during compilation. It uses 16various system-dependent variables used during compilation. It uses
@@ -26,9 +23,9 @@ debugging `configure').
26 23
27 It can also use an optional file (typically called `config.cache' 24 It can also use an optional file (typically called `config.cache'
28and enabled with `--cache-file=config.cache' or simply `-C') that saves 25and enabled with `--cache-file=config.cache' or simply `-C') that saves
29the results of its tests to speed up reconfiguring. Caching is 26the results of its tests to speed up reconfiguring. (Caching is
30disabled by default to prevent problems with accidental use of stale 27disabled by default to prevent problems with accidental use of stale
31cache files. 28cache files.)
32 29
33 If you need to do unusual things to compile the package, please try 30 If you need to do unusual things to compile the package, please try
34to figure out how `configure' could check whether to do them, and mail 31to figure out how `configure' could check whether to do them, and mail
@@ -38,17 +35,20 @@ some point `config.cache' contains results you don't want to keep, you
38may remove or edit it. 35may remove or edit it.
39 36
40 The file `configure.ac' (or `configure.in') is used to create 37 The file `configure.ac' (or `configure.in') is used to create
41`configure' by a program called `autoconf'. You need `configure.ac' if 38`configure' by a program called `autoconf'. You only need
42you want to change it or regenerate `configure' using a newer version 39`configure.ac' if you want to change it or regenerate `configure' using
43of `autoconf'. 40a newer version of `autoconf'.
44 41
45The simplest way to compile this package is: 42The simplest way to compile this package is:
46 43
47 1. `cd' to the directory containing the package's source code and type 44 1. `cd' to the directory containing the package's source code and type
48 `./configure' to configure the package for your system. 45 `./configure' to configure the package for your system. If you're
46 using `csh' on an old version of System V, you might need to type
47 `sh ./configure' instead to prevent `csh' from trying to execute
48 `configure' itself.
49 49
50 Running `configure' might take a while. While running, it prints 50 Running `configure' takes awhile. While running, it prints some
51 some messages telling which features it is checking for. 51 messages telling which features it is checking for.
52 52
53 2. Type `make' to compile the package. 53 2. Type `make' to compile the package.
54 54
@@ -67,57 +67,42 @@ The simplest way to compile this package is:
67 all sorts of other programs in order to regenerate files that came 67 all sorts of other programs in order to regenerate files that came
68 with the distribution. 68 with the distribution.
69 69
70 6. Often, you can also type `make uninstall' to remove the installed
71 files again.
72
73Compilers and Options 70Compilers and Options
74===================== 71=====================
75 72
76 Some systems require unusual options for compilation or linking that 73Some systems require unusual options for compilation or linking that the
77the `configure' script does not know about. Run `./configure --help' 74`configure' script does not know about. Run `./configure --help' for
78for details on some of the pertinent environment variables. 75details on some of the pertinent environment variables.
79 76
80 You can give `configure' initial values for configuration parameters 77 You can give `configure' initial values for configuration parameters
81by setting variables in the command line or in the environment. Here 78by setting variables in the command line or in the environment. Here
82is an example: 79is an example:
83 80
84 ./configure CC=c99 CFLAGS=-g LIBS=-lposix 81 ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
85 82
86 *Note Defining Variables::, for more details. 83 *Note Defining Variables::, for more details.
87 84
88Compiling For Multiple Architectures 85Compiling For Multiple Architectures
89==================================== 86====================================
90 87
91 You can compile the package for more than one kind of computer at the 88You can compile the package for more than one kind of computer at the
92same time, by placing the object files for each architecture in their 89same time, by placing the object files for each architecture in their
93own directory. To do this, you can use GNU `make'. `cd' to the 90own directory. To do this, you must use a version of `make' that
91supports the `VPATH' variable, such as GNU `make'. `cd' to the
94directory where you want the object files and executables to go and run 92directory where you want the object files and executables to go and run
95the `configure' script. `configure' automatically checks for the 93the `configure' script. `configure' automatically checks for the
96source code in the directory that `configure' is in and in `..'. 94source code in the directory that `configure' is in and in `..'.
97 95
98 With a non-GNU `make', it is safer to compile the package for one 96 If you have to use a `make' that does not support the `VPATH'
99architecture at a time in the source code directory. After you have 97variable, you have to compile the package for one architecture at a
100installed the package for one architecture, use `make distclean' before 98time in the source code directory. After you have installed the
101reconfiguring for another architecture. 99package for one architecture, use `make distclean' before reconfiguring
102 100for another architecture.
103 On MacOS X 10.5 and later systems, you can create libraries and
104executables that work on multiple system types--known as "fat" or
105"universal" binaries--by specifying multiple `-arch' options to the
106compiler but only a single `-arch' option to the preprocessor. Like
107this:
108
109 ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
110 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
111 CPP="gcc -E" CXXCPP="g++ -E"
112
113 This is not guaranteed to produce working output in all cases, you
114may have to build one architecture at a time and combine the results
115using the `lipo' tool if you have problems.
116 101
117Installation Names 102Installation Names
118================== 103==================
119 104
120 By default, `make install' installs the package's commands under 105By default, `make install' installs the package's commands under
121`/usr/local/bin', include files under `/usr/local/include', etc. You 106`/usr/local/bin', include files under `/usr/local/include', etc. You
122can specify an installation prefix other than `/usr/local' by giving 107can specify an installation prefix other than `/usr/local' by giving
123`configure' the option `--prefix=PREFIX'. 108`configure' the option `--prefix=PREFIX'.
@@ -140,7 +125,7 @@ option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
140Optional Features 125Optional Features
141================= 126=================
142 127
143 Some packages pay attention to `--enable-FEATURE' options to 128Some packages pay attention to `--enable-FEATURE' options to
144`configure', where FEATURE indicates an optional part of the package. 129`configure', where FEATURE indicates an optional part of the package.
145They may also pay attention to `--with-PACKAGE' options, where PACKAGE 130They may also pay attention to `--with-PACKAGE' options, where PACKAGE
146is something like `gnu-as' or `x' (for the X Window System). The 131is something like `gnu-as' or `x' (for the X Window System). The
@@ -152,46 +137,14 @@ find the X include and library files automatically, but if it doesn't,
152you can use the `configure' options `--x-includes=DIR' and 137you can use the `configure' options `--x-includes=DIR' and
153`--x-libraries=DIR' to specify their locations. 138`--x-libraries=DIR' to specify their locations.
154 139
155Particular systems
156==================
157
158 On HP-UX, the default C compiler is not ANSI C compatible. If GNU
159CC is not installed, it is recommended to use the following options in
160order to use an ANSI C compiler:
161
162 ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
163
164and if that doesn't work, install pre-built binaries of GCC for HP-UX.
165
166 On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
167parse its `<wchar.h>' header file. The option `-nodtk' can be used as
168a workaround. If GNU CC is not installed, it is therefore recommended
169to try
170
171 ./configure CC="cc"
172
173and if that doesn't work, try
174
175 ./configure CC="cc -nodtk"
176
177 On Solaris, don't put `/usr/ucb' early in your `PATH'. This
178directory contains several dysfunctional programs; working variants of
179these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
180in your `PATH', put it _after_ `/usr/bin'.
181
182 On Haiku, software installed for all users goes in `/boot/common',
183not `/usr/local'. It is recommended to use the following options:
184
185 ./configure --prefix=/boot/common
186
187Specifying the System Type 140Specifying the System Type
188========================== 141==========================
189 142
190 There may be some features `configure' cannot figure out 143There may be some features `configure' cannot figure out automatically,
191automatically, but needs to determine by the type of machine the package 144but needs to determine by the type of machine the package will run on.
192will run on. Usually, assuming the package is built to be run on the 145Usually, assuming the package is built to be run on the _same_
193_same_ architectures, `configure' can figure that out, but if it prints 146architectures, `configure' can figure that out, but if it prints a
194a message saying it cannot guess the machine type, give it the 147message saying it cannot guess the machine type, give it the
195`--build=TYPE' option. TYPE can either be a short name for the system 148`--build=TYPE' option. TYPE can either be a short name for the system
196type, such as `sun4', or a canonical name which has the form: 149type, such as `sun4', or a canonical name which has the form:
197 150
@@ -199,8 +152,7 @@ type, such as `sun4', or a canonical name which has the form:
199 152
200where SYSTEM can have one of these forms: 153where SYSTEM can have one of these forms:
201 154
202 OS 155 OS KERNEL-OS
203 KERNEL-OS
204 156
205 See the file `config.sub' for the possible values of each field. If 157 See the file `config.sub' for the possible values of each field. If
206`config.sub' isn't included in this package, then this package doesn't 158`config.sub' isn't included in this package, then this package doesn't
@@ -218,9 +170,9 @@ eventually be run) with `--host=TYPE'.
218Sharing Defaults 170Sharing Defaults
219================ 171================
220 172
221 If you want to set default values for `configure' scripts to share, 173If you want to set default values for `configure' scripts to share, you
222you can create a site shell script called `config.site' that gives 174can create a site shell script called `config.site' that gives default
223default values for variables like `CC', `cache_file', and `prefix'. 175values for variables like `CC', `cache_file', and `prefix'.
224`configure' looks for `PREFIX/share/config.site' if it exists, then 176`configure' looks for `PREFIX/share/config.site' if it exists, then
225`PREFIX/etc/config.site' if it exists. Or, you can set the 177`PREFIX/etc/config.site' if it exists. Or, you can set the
226`CONFIG_SITE' environment variable to the location of the site script. 178`CONFIG_SITE' environment variable to the location of the site script.
@@ -229,7 +181,7 @@ A warning: not all `configure' scripts look for a site script.
229Defining Variables 181Defining Variables
230================== 182==================
231 183
232 Variables not defined in a site shell script can be set in the 184Variables not defined in a site shell script can be set in the
233environment passed to `configure'. However, some packages may run 185environment passed to `configure'. However, some packages may run
234configure again during the build, and the customized values of these 186configure again during the build, and the customized values of these
235variables may be lost. In order to avoid this problem, you should set 187variables may be lost. In order to avoid this problem, you should set
@@ -238,29 +190,21 @@ them in the `configure' command line, using `VAR=value'. For example:
238 ./configure CC=/usr/local2/bin/gcc 190 ./configure CC=/usr/local2/bin/gcc
239 191
240causes the specified `gcc' to be used as the C compiler (unless it is 192causes the specified `gcc' to be used as the C compiler (unless it is
241overridden in the site shell script). 193overridden in the site shell script). Here is a another example:
242 194
243Unfortunately, this technique does not work for `CONFIG_SHELL' due to 195 /bin/bash ./configure CONFIG_SHELL=/bin/bash
244an Autoconf bug. Until the bug is fixed you can use this workaround:
245 196
246 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash 197Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
198configuration-related scripts to be executed by `/bin/bash'.
247 199
248`configure' Invocation 200`configure' Invocation
249====================== 201======================
250 202
251 `configure' recognizes the following options to control how it 203`configure' recognizes the following options to control how it operates.
252operates.
253 204
254`--help' 205`--help'
255`-h' 206`-h'
256 Print a summary of all of the options to `configure', and exit. 207 Print a summary of the options to `configure', and exit.
257
258`--help=short'
259`--help=recursive'
260 Print a summary of the options unique to this package's
261 `configure', and exit. The `short' variant lists options used
262 only in the top level, while the `recursive' variant lists options
263 also present in any nested packages.
264 208
265`--version' 209`--version'
266`-V' 210`-V'
@@ -287,16 +231,6 @@ operates.
287 Look for the package's source code in directory DIR. Usually 231 Look for the package's source code in directory DIR. Usually
288 `configure' can determine that directory automatically. 232 `configure' can determine that directory automatically.
289 233
290`--prefix=DIR'
291 Use DIR as the installation prefix. *Note Installation Names::
292 for more details, including other options available for fine-tuning
293 the installation locations.
294
295`--no-create'
296`-n'
297 Run the configure checks, but stop before creating any output
298 files.
299
300`configure' also accepts some other, not widely useful, options. Run 234`configure' also accepts some other, not widely useful, options. Run
301`configure --help' for more details. 235`configure --help' for more details.
302 236
diff --git a/legacy/eeze/README b/legacy/eeze/README
index 5e3ab0ec81..cfe5068a2e 100644
--- a/legacy/eeze/README
+++ b/legacy/eeze/README
@@ -1,3 +1,28 @@
1eeze v?.?? 1Embryo 1.0.0-alpha ALPHA
2 2
3eeze is a library to simplify the use of devices. Dependencies may vary, use at your own risk, i before e except after c. 3******************************************************************************
4
5 FOR ANY ISSUES PLEASE EMAIL:
6 enlightenment-devel@lists.sourceforge.net
7
8******************************************************************************
9
10
11Requirements:
12-------------
13
14Must:
15 libc
16 ecore (at least 1.0.0)
17
18Eeze is a library for handling devicekit and friends .... disco-stu...
19fill the rest in!
20
21------------------------------------------------------------------------------
22COMPILING AND INSTALLING:
23
24 ./configure
25 make
26(as root unless youa re installing in your users directories):
27 make install
28
diff --git a/legacy/eeze/configure.ac b/legacy/eeze/configure.ac
index a2c820526b..2fe8aa04b0 100644
--- a/legacy/eeze/configure.ac
+++ b/legacy/eeze/configure.ac
@@ -1,14 +1,14 @@
1##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--## 1##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
2##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--## 2##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
3m4_define([v_maj], [0]) 3m4_define([v_maj], [1])
4m4_define([v_min], [2]) 4m4_define([v_min], [0])
5m4_define([v_mic], [0]) 5m4_define([v_mic], [0])
6m4_define([v_rev], m4_esyscmd([(svnversion "${SVN_REPO_PATH:-.}" | grep -v export || echo 0) | awk -F : '{printf("%s\n", $1);}' | tr -d ' :MSP\n'])) 6m4_define([v_rev], m4_esyscmd([(svnversion "${SVN_REPO_PATH:-.}" | grep -v export || echo 0) | awk -F : '{printf("%s\n", $1);}' | tr -d ' :MSP\n']))
7m4_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']))]) 7m4_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']))])
8##-- When released, remove the dnl on the below line 8##-- When released, remove the dnl on the below line
9dnl m4_undefine([v_rev]) 9m4_undefine([v_rev])
10##-- When doing snapshots - change soname. remove dnl on below line 10##-- When doing snapshots - change soname. remove dnl on below line
11dnl m4_define([relname], [ver-pre-svn-06]) 11dnl dnl m4_define([relname], [ver-pre-svn-06])
12dnl m4_define([v_rel], [-release relname]) 12dnl m4_define([v_rel], [-release relname])
13##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--## 13##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
14m4_ifdef([v_rev], [m4_define([v_ver], [v_maj.v_min.v_mic.v_rev])], [m4_define([v_ver], [v_maj.v_min.v_mic])]) 14m4_ifdef([v_rev], [m4_define([v_ver], [v_maj.v_min.v_mic.v_rev])], [m4_define([v_ver], [v_maj.v_min.v_mic])])
@@ -18,8 +18,7 @@ m4_define([lt_age], v_min)
18##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--## 18##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
19##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--## 19##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
20 20
21AC_INIT([eeze], [v_ver], [enlightenment-devel@lists.sourceforge.net]) 21AC_INIT([eeze], [v_ver-alpha], [enlightenment-devel@lists.sourceforge.net])
22release="ver-pre-svn-05"
23AC_PREREQ([2.52]) 22AC_PREREQ([2.52])
24AC_CONFIG_SRCDIR([configure.ac]) 23AC_CONFIG_SRCDIR([configure.ac])
25AC_CONFIG_MACRO_DIR([m4]) 24AC_CONFIG_MACRO_DIR([m4])
@@ -53,7 +52,7 @@ AC_SUBST(VMAJ)
53 52
54### Needed information 53### Needed information
55 54
56requirement_eeze="ecore libudev" 55requirement_eeze="ecore >= 1.0.0 libudev"
57 56
58 57
59### Checks for programs 58### Checks for programs
@@ -78,7 +77,7 @@ EFL_CHECK_DOXYGEN([build_doc="yes"], [build_doc="no"])
78 77
79### Checks for libraries 78### Checks for libraries
80 79
81PKG_CHECK_MODULES([ECORE], [ecore]) 80PKG_CHECK_MODULES([ECORE], [ecore >= 1.0.0])
82PKG_CHECK_MODULES([LIBUDEV], [libudev]) 81PKG_CHECK_MODULES([LIBUDEV], [libudev])
83 82
84udev_version=$(pkg-config libudev --modversion) 83udev_version=$(pkg-config libudev --modversion)
diff --git a/legacy/eeze/src/lib/Eeze.h b/legacy/eeze/src/lib/Eeze.h
index 4237a3d0e3..2e02adcd09 100644
--- a/legacy/eeze/src/lib/Eeze.h
+++ b/legacy/eeze/src/lib/Eeze.h
@@ -161,13 +161,18 @@ typedef enum
161struct Eeze_Udev_Watch; 161struct Eeze_Udev_Watch;
162typedef struct Eeze_Udev_Watch Eeze_Udev_Watch; 162typedef struct Eeze_Udev_Watch Eeze_Udev_Watch;
163 163
164typedef struct _Eeze_Version 164#define EEZE_VERSION_MAJOR 1
165 { 165#define EEZE_VERSION_MINOR 0
166 int major; 166
167 int minor; 167 typedef struct _Eeze_Version
168 int micro; 168 {
169 int revision; 169 int major;
170 } Eeze_Version; 170 int minor;
171 int micro;
172 int revision;
173 } Eeze_Version;
174
175 EAPI extern Eeze_Version *eeze_version;
171 176
172/** 177/**
173 * @addtogroup watch 178 * @addtogroup watch
@@ -175,11 +180,6 @@ typedef struct _Eeze_Version
175 */ 180 */
176typedef void(*Eeze_Udev_Watch_Cb)(const char *, Eeze_Udev_Event, void *, Eeze_Udev_Watch *); 181typedef void(*Eeze_Udev_Watch_Cb)(const char *, Eeze_Udev_Event, void *, Eeze_Udev_Watch *);
177 182
178#define EEZE_VERSION_MAJOR 0
179#define EEZE_VERSION_MINOR 2
180
181 EAPI extern Eeze_Version *eeze_version;
182
183 EAPI int eeze_init(void); 183 EAPI int eeze_init(void);
184 EAPI int eeze_shutdown(void); 184 EAPI int eeze_shutdown(void);
185 185