elm_code_widget is causing a lot of trouble as it's relying on internal
access to elementary, without being built as part of elementary.so. Many
EAPI symbols are exported that shouldn't need to be, as they are only
internals of elm.
typedef struct _Elm_Label_Data Elm_Label_Data;
typedef struct _Elm_Translate_String_Data Elm_Translate_String_Data;
-Eina_Bool _elm_legacy_add = EINA_FALSE;
+/* FIXME: EAPI because of elm_code_widget test case */
+EAPI Eina_Bool _elm_legacy_add = EINA_FALSE;
struct _Elm_Event_Cb_Data
{
/* Internal hack to mark legacy objects as such before construction.
* No need for TLS: Only UI objects created in the main loop matter. */
-extern Eina_Bool _elm_legacy_add;
+EAPI Eina_Bool _elm_legacy_add;
#define elm_legacy_add(k, p, ...) ({ _elm_legacy_add = 1; \
efl_add(k, p, efl_canvas_object_legacy_ctor(efl_added), ##__VA_ARGS__); })