Eeze Device Library.

\begin{DoxyDate}{Date}
2010 (created)
\end{DoxyDate}
\hypertarget{eeze_main_eeze_toc}{}\doxysection{Table of Contents}\label{eeze_main_eeze_toc}
\begin{DoxyItemize}
\item \mbox{\hyperlink{eeze_main_eeze_main_intro}{Introduction}} \item \mbox{\hyperlink{eeze_main_eeze_main_compiling}{How to compile}} \item \mbox{\hyperlink{eeze_main_eeze_main_next_steps}{Next Steps}}\end{DoxyItemize}
\hypertarget{eeze_main_eeze_main_intro}{}\doxysection{Introduction}\label{eeze_main_eeze_main_intro}
Eeze is a library for manipulating devices through udev with a simple and fast api. It interfaces directly with libudev, avoiding such middleman daemons as udisks/upower or hal, to immediately gather device information the instant it becomes known to the system. This can be used to determine such things as\+:

\begin{DoxyItemize}
\item If a cdrom has a disk inserted \item The temperature of a cpu core \item The remaining power left in a battery \item The current power consumption of various parts \item Monitor in realtime the status of peripheral devices\end{DoxyItemize}
Each of the above examples can be performed by using only a single eeze function, as one of the primary focuses of the library is to reduce the complexity of managing devices.\hypertarget{eeze_main_eeze_main_compiling}{}\doxysection{How to compile}\label{eeze_main_eeze_main_compiling}
Eeze is a library your application links to. The procedure for this is very simple. You simply have to compile your application with the appropriate compiler flags that the {\ttfamily pkg-\/config} script outputs. For example\+:

Compiling C or C++ files into object files\+:

\begin{DoxyVerb}gcc -c -o main.o main.c `pkg-config --cflags eeze`
\end{DoxyVerb}


Linking object files into a binary executable\+:

\begin{DoxyVerb}gcc -o my_application main.o `pkg-config --libs eeze`
\end{DoxyVerb}


See \mbox{\hyperlink{pkgconfig}{pkgconfig}}\hypertarget{eeze_main_eeze_main_next_steps}{}\doxysection{Next Steps}\label{eeze_main_eeze_main_next_steps}
After you understood what Eeze is and installed it in your system you should proceed understanding the programming interface. We\textquotesingle{}d recommend you to take a while to learn \mbox{\hyperlink{group__Eina}{Eina}} and \mbox{\hyperlink{group__Ecore}{Ecore}} as they convenient and Eeze provides integration with it.

Recommended reading\+:

\begin{DoxyItemize}
\item \mbox{\hyperlink{Eeze_8h}{Eeze functions }} \item \mbox{\hyperlink{group__Eeze__Udev}{udev}} UDEV functions \item \mbox{\hyperlink{group__Eeze__Watch}{Watch}} Functions that watch for events \item \mbox{\hyperlink{group__Eeze__Syspath}{Syspath}} Functions that accept a device /sys/ path \item \mbox{\hyperlink{group__Eeze__Find}{Find}} Functions which find types of devices \item \mbox{\hyperlink{group__Eeze__Disk}{Disk}} Disk functions \item \mbox{\hyperlink{group__Eeze__Net}{Net}} Net functions \item \mbox{\hyperlink{group__Eeze__Sensor}{Sensor}} Sensor functions \end{DoxyItemize}
