Re: How is symbol visibility set in KF5 and KDE?
Kevin Funk <[email protected]>
| Newsgroups | gmane.comp.kde.devel.core,gmane.comp.kde.devel.bindings,gmane.comp.kde.devel.frameworks |
|---|---|
| Message-ID | <4692946.AFX5LxBmcg@kerberos> |
On Wednesday, 15 November 2017 15:54:17 CET Shaheed Haque wrote: > Hi all, > > I just realised that the Python binding effort is not setting the default > visibility for symbols using the -fvisibility=xxx option when processing > the header files [1]. Of course I can see the export macros set by the > likes of attica_exports.h, but I don't see where the compiler default is > set. Can somebody kindly point that out? It's configured in extra-cmake-modules.git: kde-modules/KDECompilerSettings.cmake 223:set(CMAKE_C_VISIBILITY_PRESET hidden) 224:set(CMAKE_CXX_VISIBILITY_PRESET hidden) 225:set(CMAKE_VISIBILITY_INLINES_HIDDEN 1) Regards, Kevin > Thanks, Shaheed > > [1] I'm also a bit mystified by the fact that I am deliberately querying > CMake for the COMPILE_FLAGS to use, but I have not seen -fvisibility > anywhere... -- Kevin Funk | [email protected] | http://kfunk.org
signature.asc
(application/pgp-signature, 163 B)
-----BEGIN PGP SIGNATURE----- iEYEABECAAYFAloMaRkACgkQxkz1axPKzl1XkgCg2C+Qye1eHFiW3COVkWQ/ANz5 ZvYAnjStRMM+zPXjlZgdBpwwX5bBNM/9 =pS85 -----END PGP SIGNATURE-----