diff options
| author | Stephan Bergmann <sbergman@redhat.com> | 2015-01-26 15:09:13 +0100 |
|---|---|---|
| committer | Stephan Bergmann <sbergman@redhat.com> | 2015-01-26 15:17:30 +0100 |
| commit | b6ee5cf707343e5393514a47c024535ea6c1b7d1 (patch) | |
| tree | 5d698152f2678d8a377926efe64596d2b382d0e2 /RepositoryExternal.mk | |
| parent | 6f762e3a26be0dae8ad65f46a4a4b7193a494242 (diff) | |
external/lib{odfgen,revenge}: Declare proper symbol visibility
...not only when building the libs themselves, but also when including their
header files from other code. (Omission only becomes obvious with hidden
function type RTTI causing false positives from Clang -fsanitize=function.) As
these external libs do not record the decision to enable visiblity in a config
header file that gets included, it appears easiest to hack that knowledge into
gbuild for now. (Note that libodfgen internally uses librevenge.)
Change-Id: I6a3a722d561b8cbce6e5b1f27d7aa2d7602f3cdf
Diffstat (limited to 'RepositoryExternal.mk')
| -rw-r--r-- | RepositoryExternal.mk | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/RepositoryExternal.mk b/RepositoryExternal.mk index 5799da2a6ed5..9789959ce363 100644 --- a/RepositoryExternal.mk +++ b/RepositoryExternal.mk @@ -1795,6 +1795,7 @@ $(call gb_LinkTarget_use_package,$(1),libodfgen) $(call gb_LinkTarget_set_include,$(1),\ -I$(call gb_UnpackedTarball_get_dir,libodfgen)/inc \ + -DLIBODFGEN_VISIBILITY \ $$(INCLUDE) \ ) $(call gb_LinkTarget_add_libs,$(1),\ @@ -1856,6 +1857,7 @@ $(call gb_LinkTarget_use_package,$(1),librevenge) $(call gb_LinkTarget_set_include,$(1),\ $(REVENGE_CFLAGS) \ + -DLIBREVENGE_VISIBILITY \ $$(INCLUDE) \ ) $(call gb_LinkTarget_add_libs,$(1),\ |