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.
This commit is contained in:
parent
aa0324af36
commit
fecc487b3b
|
@ -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;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue