When we load a plugin any symbols we export come before its symbols. We don't want a plugin to accidentally rely on our symbols, or more generally we don't want to export any symbols.
The -fvisibility=hidden flag is maybe supposed to do this (see discussion on http://gcc.gnu.org/wiki/Visibility ), but I tried building both with and without it and found that: - in debug builds, objdump -T shows all of our symbols, regardless of the flags I pass to gcc or strip - in release builds, objdump -T doesn't show us exporting symbols, regardless of the flags I pass to gcc The resulting release binaries are within 1kb of each other. I don't really know what I'm doing, so my guess is that some other compilation flags we're using already produce the intended effect. Clearly this flag does *something* as the resulting binaries have slightly different sizes, but maybe it's not intended to apply to binaries or maybe it doesn't in my gcc (4.2.4). *shrug*, waste of an evening but I was doing something else all the while anyway --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
