https://travis-ci.org/Enlightenment/efl/jobs/416583687 looks like circular dependency between evas modules and ecore-cocoa
Description
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | bu5hm4n | T7175 meson build system | ||
Resolved | bu5hm4n | T6609 Port efl to meson | ||
Resolved | zmike | T7306 cocoa build broken |
Yeah, ecore_cocoa does a bit of weird things, ecore_cocoa uses the function evas_textblock_text_markup_to_utf8. It should not.
In general: A type like MARKUP should stop at the level of elm, or ecore_evas ... but should never be used in ecore_cocoa.
I agree that it probably should not, but this is how the code is written.
An alternative here I suppose would be to make the code for that function a standalone in a static library?
Or just quick and dirty dlsym'ing evas_textblock_text_markup_to_utf8 ?
Its not nice, but a solution...
I don't know if this will help, but ecore_cocoa_clipboard_set() (that calls evas_textblock_text_markup_to_utf8) is beta API (the whole cocoa clipboard API is). It was (badly) designed to be used by Elementary only. Maybe the caller of this function can run the evas_textblock_text_markup_to_utf8() first, and pass its output as the data parameter?