forked from enlightenment/efl
72 lines
2.5 KiB
Plaintext
72 lines
2.5 KiB
Plaintext
Ecore @VERSION@
|
|
|
|
Requirements:
|
|
-------------
|
|
|
|
Must:
|
|
libc libm
|
|
|
|
Recommended:
|
|
libX11 libXext libXcursor libXprint libXinerama libXrandr libXss libXrender
|
|
libXcomposite libXfixes libXdamage libXdpms libXtest OpenSSL CURL
|
|
|
|
Optional:
|
|
XCB SDL DirectFB
|
|
|
|
Ecore is a clean and tiny event loop library with many modules to do
|
|
lots of convenient things for a programmer, to save time and effort.
|
|
|
|
It's small and lean, designed to work on embedded systems all the way
|
|
to large and powerful multi-cpu workstations. It serialises all system
|
|
signals, events etc. into a single event queue, that is easily
|
|
processed without needing to worry about concurrency. A properly
|
|
written, event-driven program using this kind of programming doesn't
|
|
need threads, nor has to worry about concurrency. It turns a program
|
|
into a state machine, and makes it very robust and easy to follow.
|
|
|
|
Ecore gives you other handy primitives, such as timers to tick over
|
|
for you and call specified functions at particular times so the
|
|
programmer can use this to do things, like animate, or time out on
|
|
connections or tasks that take too long etc.
|
|
|
|
Idle handlers are provided too, as well as calls on entering an idle
|
|
state (often a very good time to update the state of the program). All
|
|
events that enter the system are passed to specific callback functions
|
|
that the program sets up to handle those events. Handling them is
|
|
simple and other Ecore modules produce more events on the queue,
|
|
coming from other sources such as file descriptors etc.
|
|
|
|
Ecore also lets you have functions called when file descriptors become
|
|
active for reading or writing, allowing for streamlined, non-blocking
|
|
IO.
|
|
|
|
------------------------------------------------------------------------------
|
|
COMPILING AND INSTALLING:
|
|
|
|
./configure
|
|
make
|
|
(as root unless youa re 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)
|
|
|
|
DEB: To build deb packages:
|
|
|
|
tar zvf @PACKAGE@-@VERSION@.tar.gz
|
|
cd @PACKAGE@-@VERSION@
|
|
dpkg-buildpackage -us -uc -rfakeroot
|
|
cd ..
|
|
rm -rf @PACKAGE@-@VERSION@
|
|
|
|
You will find all the debian source, binary etc. packages put in the directory
|
|
where you first untarred the source tarball.
|