From 0218957eb5c22fd5a514545149ccb2275a3ed0d5 Mon Sep 17 00:00:00 2001 From: Chris Robinson Date: Wed, 8 Dec 2010 02:32:09 -0800 Subject: Use "internal" visibility by default All functions callable by apps, directly or indirectly (eg, through function pointers), are marked as "protected", and internal visibility can provide benefits over hidden when we know functions won't be called by other modules. --- CMakeLists.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'CMakeLists.txt') diff --git a/CMakeLists.txt b/CMakeLists.txt index 0842aae7..1aa568f4 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -133,7 +133,7 @@ ELSE() CHECK_C_SOURCE_COMPILES("int foo() __attribute__((visibility(\"default\"))); int main() {return 0;}" HAVE_GCC_VISIBILITY) IF(HAVE_GCC_VISIBILITY) - ADD_DEFINITIONS(-fvisibility=hidden -DHAVE_GCC_VISIBILITY) + ADD_DEFINITIONS(-fvisibility=internal -DHAVE_GCC_VISIBILITY) ENDIF() ENDIF() ENDIF() -- cgit v1.2.3