summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJean-Philippe Andre <jp.andre@samsung.com>2015-03-05 16:16:11 +0900
committerJean-Philippe Andre <jp.andre@samsung.com>2015-03-05 16:19:18 +0900
commitfecc487b3b6dd5a45f28b8ff888446fbf4381c2c (patch)
treeb2fa0998a7a6f0da4f972de64379a3148b5bab44
parentaa0324af36973be273a469f7bfae152f8774c57f (diff)
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.
-rw-r--r--src/modules/evas/engines/gl_common/evas_gl_core.c3
1 files changed, 2 insertions, 1 deletions
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)
1497 return evgl_engine; 1497 return evgl_engine;
1498 1498
1499error: 1499error:
1500 ERR("Failed to initialize EvasGL!");
1500 if (evgl_engine) 1501 if (evgl_engine)
1501 { 1502 {
1502 eina_hash_free(evgl_engine->safe_extensions); 1503 eina_hash_free(evgl_engine->safe_extensions);
@@ -1518,7 +1519,7 @@ evgl_engine_shutdown(void *eng_data)
1518 // Check if engine is valid 1519 // Check if engine is valid
1519 if (!evgl_engine) 1520 if (!evgl_engine)
1520 { 1521 {
1521 ERR("EVGL Engine not valid!"); 1522 EINA_LOG_INFO("EvasGL Engine is not initialized.");
1522 return; 1523 return;
1523 } 1524 }
1524 1525