Tizen Native API  5.5
Ecore initialization, shutdown functions and reset on fork.

Functions

int ecore_init (void)
int ecore_shutdown (void)
EWAPI void efl_build_version_set (int vmaj, int vmin, int vmic, int revision, const char *flavor, const char *build_id)
 Inform EFL of the version this application was built for.

Function Documentation

int ecore_init ( void  )

Sets up connections, signal handlers, sockets etc.

Returns:
1 or greater on success, 0 otherwise.

This function sets up all singal handlers and the basic event loop. If it succeeds, 1 will be returned, otherwise 0 will be returned.

 #include <Ecore.h>

 int main(int argc, char **argv)
 {
   if (!ecore_init())
   {
     printf("ERROR: Cannot init Ecore!\n");
     return -1;
   }
   ecore_main_loop_begin();
   ecore_shutdown();
 }

This function is affected by some environment variables:

  • ECORE_NO_SYSTEM_MODULES=1 may be used to temporarily disable system modules, often useful for debug.
  • ECORE_FPS_DEBUG=1 prints frames per second, usefult to detect lags and blocking calls.
  • ECORE_MEM_STAT=1 will generate ecore_mem_stat.${PID} file with memory statistics.
  • ECORE_ERROR_ABORT=1 will abort on errors.

This function will call eina_init(), so other environment variables may apply.

Since :
3.0f(2.3.1)
Examples:
ecore_con_client_simple_example.c, ecore_con_server_simple_example.c, ecore_con_url_cookies_example.c, ecore_con_url_download_example.c, ecore_con_url_headers_example.c, ecore_event_example_01.c, ecore_event_example_02.c, ecore_exe_example.c, ecore_exe_example_child.c, ecore_fd_handler_example.c, ecore_fd_handler_gnutls_example.c, ecore_idler_example.c, ecore_job_example.c, ecore_pipe_gstreamer_example.c, ecore_pipe_simple_example.c, ecore_poller_example.c, ecore_thread_example.c, ecore_time_functions_example.c, ecore_timer_example.c, and eina_tiler_01.c.
int ecore_shutdown ( void  )

Shuts down connections, signal handlers sockets etc.

Returns:
0 if ecore shuts down, greater than 0 otherwise. This function shuts down all things set up in ecore_init() and cleans up all event queues, handlers, filters, timers, idlers, idle enterers/exiters etc. set up after ecore_init() was called.

Do not call this function from any callback that may be called from the main loop, as the main loop will then fall over and not function properly.

Since :
3.0f(2.3.1)
Examples:
ecore_con_client_simple_example.c, ecore_con_server_simple_example.c, ecore_con_url_cookies_example.c, ecore_con_url_download_example.c, ecore_con_url_headers_example.c, ecore_event_example_02.c, ecore_exe_example.c, ecore_exe_example_child.c, ecore_fd_handler_example.c, ecore_idler_example.c, ecore_job_example.c, ecore_pipe_gstreamer_example.c, ecore_pipe_simple_example.c, ecore_poller_example.c, ecore_thread_example.c, ecore_time_functions_example.c, ecore_timer_example.c, and eina_tiler_01.c.
EWAPI void efl_build_version_set ( int  vmaj,
int  vmin,
int  vmic,
int  revision,
const char *  flavor,
const char *  build_id 
)

Inform EFL of the version this application was built for.

This function will propagate the events on the main loop. So you should call ecore_init() first, then register your callback on EFL_LOOP_EVENT_ARGUMENTS and finally call ecore_init_ex().

Once you are shuting down your program, you should symmetrically call ecore_shutdown_ex(). Shuts down connections, signal handlers sockets etc.

Returns:
0 if ecore shuts down, greater than 0 otherwise. This function shuts down all things set up in ecore_init_ex() and cleans up all event queues, handlers, filters, timers, idlers, idle enterers/exiters etc. set up after ecore_init_ex() was called.

Do not call this function from any callback that may be called from the main loop, as the main loop will then fall over and not function properly.

Note: This function should be called in symetric to ecore_init_ex() This is transparently called from $EFL_MAIN().

Since (EFL) :
1.18 (as beta)