\begin{DoxyDate}{Date}
2012 (created)
\end{DoxyDate}
\hypertarget{eina_cxx_main_toc}{}\section{Table of Contents}\label{eina_cxx_main_toc}
\begin{DoxyItemize}
\item \hyperlink{eo_main_eo_main_intro}{Introduction} \item \hyperlink{eo_main_eo_main_compiling}{How to compile} \item \hyperlink{eo_main_eo_main_next_steps}{Next Steps} \item \hyperlink{eo_main_eo_main_intro_example}{Introductory Example}\end{DoxyItemize}
\hypertarget{eo_main_eo_main_intro}{}\section{Introduction}\label{eo_main_eo_main_intro}
The Eo generic object system. It was designed to be the base object system for the E\+FL.\hypertarget{eo_main_eo_main_compiling}{}\section{How to compile}\label{eo_main_eo_main_compiling}
Eo 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 eo`
\end{DoxyVerb}


Linking object files into a binary executable\+:

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


See \hyperlink{pkgconfig}{pkgconfig}\hypertarget{eo_main_eo_main_next_steps}{}\section{Next Steps}\label{eo_main_eo_main_next_steps}
After you understood what Eo is and installed it in your system you should proceed understanding the programming interface.

Recommended reading\+:

\begin{DoxyItemize}
\item \hyperlink{group__Eo__Class__Base}{Eo\textquotesingle{}s Base class.} \item \hyperlink{group__Eo__Class}{Eo Class} \item \hyperlink{group__Eo__Events}{Eo\textquotesingle{}s Event Handling} \item Eo\+\_\+\+Composite\+\_\+\+Objects\end{DoxyItemize}
\hypertarget{eo_main_eo_main_intro_example}{}\section{Introductory Example}\label{eo_main_eo_main_intro_example}
\hyperlink{Eo_Tutorial}{Eo Tutorial} 