Databases
StackOverflow2013
Postsdbo
POSymbol hiding in static libraries built with Xcode
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSymbol hiding in static libraries built with Xcode
    primarykey
    data
    text
    <p>I'm trying to figure out whether I can build a static library that hides all of its internal objects and functions, etc, except for the interfaces I want to export. I'm experimenting with Xcode (gcc 4.2).</p> <p>I've used the <code>__attribute__((visibility("hidden")))</code> attribute on some C++ classes per <a href="http://developer.apple.com/mac/library/documentation/DeveloperTools/Conceptual/CppRuntimeEnv/Articles/SymbolVisibility.html" rel="noreferrer">this documentation</a>. I've also defined little helper C functions as being file-local (static), etc.</p> <p>However, when I run <code>strings</code> on the resulting .a library file, even when compiled in Release configuration, I still see the names of my ostensibly-hidden classes, with their method names, and even the names of file-local functions strewn around in there as well. </p> <p>I've added the <code>-fvisibility=hidden</code> and even <code>-fno-rtti</code> to the gcc flags. While this reduces some of the strings, the class names, method names, and static functions names are all still in there in plain or mangled-but-readable form. </p> <p>Is there a reliable way to get the compiler to build this stuff without having the string names of all the internal stuff emitted into the binary? It shouldn't be necessary to have for any external clients linking in.</p> <p>(To clarify: I'm asking about obfuscation of internal naming, versus literal export binding needs. I'm disconcerted that all the internal workings are visible via the <code>strings</code> command, regardless of whether these symbols are formally exported or not.)</p> <p>Thanks.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjww
    1. USBen Zotto
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSymbol hiding in static libraries built with Xcode
      1. USDmitry Krivenok
      1. VTFavorite
    2. VO
      singulars
      1. POSymbol hiding in static libraries built with Xcode
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSymbol hiding in static libraries built with Xcode
      1. USGregory Pakosz
      1. VTFavorite
    1. COIf RTTI is enabled, all class names are going to be embedded no matter what, in order to make `type_info::name()` work. You could try recompiling with `-fno-rtti` and see if it makes a difference. Of course, if you are using `dynamic_cast` anywhere, this won't work.
      singulars
      1. POSymbol hiding in static libraries built with Xcode
      1. USThomas
    2. COThanks for the hint. Tried this, but all the names are still in there in mangled form.
      singulars
      1. POSymbol hiding in static libraries built with Xcode
      1. USBen Zotto
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload