evil: Rename EAPI macro to EVIL_API in Evil library

Authored by felipealmeida on Nov 12 2020, 8:47 AM.


evil: Rename EAPI macro to EVIL_API in Evil library

Patch from a series of patches to rename EAPI symbols to specific
library DSOs.

EAPI was designed to be able to pass

__attribute__ ((visibility ("default")))``` for symbols with
GCC, which would mean that even if -fvisibility=hidden was used
when compiling the library, the needed symbols would get exported.

MSVC __almost__ works like GCC (or mingw) in which you can
declare everything as export and it will just work (slower, but
it will work). But there's a caveat: global variables will not
work the same way for MSVC, but works for mingw and GCC.

For global variables (as opposed to functions), MSVC requires
correct DSO visibility for MSVC: instead of declaring a symbol as
export for everything, you need to declare it as import when
importing from another DSO and export when defining it locally.

With current EAPI definitions, we get the following example
working in mingw and MSVC (observe it doesn't define any global
variables as exported symbols).

Example 1:

EAPI void foo(void);

EAPI void bar()


EAPI void foo()
  printf ("foo\n");

This works fine with API defined as __declspec(dllexport) in both
cases and for gcc defining as


However, the following:
Example 2:


EAPI extern int foo;
EAPI void foobar(void);

EAPI void bar()
  foo = 5;


EAPI int foo = 0;
EAPI void foobar()
  printf ("foo %d\n", foo);

This will work on mingw but will not work for MSVC. And that's why
EAPI is the only solution that worked for MSVC.

Co-authored-by: João Paulo Taylor Ienczak Zanette <jpaulotiz@gmail.com>
Co-authored-by: Ricardo Campos <ricardo.campos@expertise.dev>
Co-authored-by: Lucas Cavalcante de Sousa <lucks.sousa@gmail.com>

Reviewers: raster, vtorri, jptiz, lucas, woohyun

Reviewed By: vtorri, jptiz

Subscribers: ProhtMeyhet, cedric, reviewers, committers

Tags: efl

Differential Revision: https://phab.enlightenment.org/D12182