forked from enlightenment/efl
ecore con url - curl is actually optional and only needs to init on use
ecore_con_utl_init is kind of pointless when we can init at the first use of a url and just have it fail. the problem is anyone initting ecore_con's url stuff will then pull in curl at that point and not laer "on first use" which is kind of nw how the dlopen fun was intended, so push it off until then.
This commit is contained in:
parent
364323881c
commit
f76d925318
|
@ -49,7 +49,6 @@ ecore_con_url_init(void)
|
|||
if (!ecore_con_init()) goto ecore_con_init_failed;
|
||||
if (!emile_init()) goto emile_init_failed;
|
||||
if (!emile_cipher_init()) goto emile_cipher_init_failed;
|
||||
_c_init();
|
||||
ECORE_CON_EVENT_URL_DATA = ecore_event_type_new();
|
||||
ECORE_CON_EVENT_URL_COMPLETE = ecore_event_type_new();
|
||||
ECORE_CON_EVENT_URL_PROGRESS = ecore_event_type_new();
|
||||
|
@ -79,7 +78,6 @@ ecore_con_url_shutdown(void)
|
|||
ECORE_CON_EVENT_URL_COMPLETE,
|
||||
ECORE_CON_EVENT_URL_PROGRESS);
|
||||
|
||||
_c_shutdown();
|
||||
emile_shutdown(); /* no emile_cipher_shutdown(), handled here */
|
||||
ecore_con_shutdown();
|
||||
ecore_shutdown();
|
||||
|
|
Loading…
Reference in New Issue