From fecc487b3b6dd5a45f28b8ff888446fbf4381c2c Mon Sep 17 00:00:00 2001 From: Jean-Philippe Andre Date: Thu, 5 Mar 2015 16:16:11 +0900 Subject: [PATCH] Evas GL: Fix CRI message on shutdown Just a simple log domain issue (EvasGL was not initialized, so ERR() would trigger a fatal error). EvasGL is now initialized on demand when a new GL surface is requested. --- src/modules/evas/engines/gl_common/evas_gl_core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/modules/evas/engines/gl_common/evas_gl_core.c b/src/modules/evas/engines/gl_common/evas_gl_core.c index e3bdccf1f5..afa2a6fdee 100644 --- a/src/modules/evas/engines/gl_common/evas_gl_core.c +++ b/src/modules/evas/engines/gl_common/evas_gl_core.c @@ -1497,6 +1497,7 @@ evgl_engine_init(void *eng_data, const EVGL_Interface *efunc) return evgl_engine; error: + ERR("Failed to initialize EvasGL!"); if (evgl_engine) { eina_hash_free(evgl_engine->safe_extensions); @@ -1518,7 +1519,7 @@ evgl_engine_shutdown(void *eng_data) // Check if engine is valid if (!evgl_engine) { - ERR("EVGL Engine not valid!"); + EINA_LOG_INFO("EvasGL Engine is not initialized."); return; } -- 2.34.1