IRC Log Viewer » #firebreath » 2015-03-24

IRC Nick Time (GMT-7) Message
kylehuff 09:03 well, reboot+rebuild, same issue, but then I noticed something I missed. the visual c++ redistributable packages were 2012, so I installed the 2013 redistributable packages, reboot+rebuild, still doesn't register.
taxilian 11:03 huh
Tim__ 15:03 taxilian
The following link flag is set up by Mac.cmake (located under cmake directory):
LINK_FLAGS "-Wl,-exported_symbols_list,${FB_ESC_ROOT_DIR}/gen_template/ExportList_plugin.txt"
Do you know what it does and why it's important to have it set?
Do you know what it does and why it's important to have it set?
taxilian 15:03 without it the plugin won't work
defines what symbols are exported
entrypoints
Tim__ 16:03 I've removed it from my plugin build and it still worked.
I've removed it from my plugin build and it still worked.
Also noticed that it was the linker flag that created a different symbol signature when it linked in sincos into my plugin.
Also noticed that it was the linker flag that created a different symbol signature when it linked in sincos into my plugin.
from
000c42e0 (__TEXT,__text) non-external (was a private external) ___sincos
to
0002f440 (__TEXT,__text) weak external ___sincos
Unfortunately, running my plugin on older OSX version continues to fail with the same loading error.
taxilian 16:03 well, let me rephrase
without it you get all symbols exported
if you set it incorrectly then it won't work
so basically it keeps people outside your plugin from calling methods inside your plugin that you don't want them to
Tim__^
Tim__^
Tim__ 16:03 OK, so that linker flag limits what symbols gets exported based on what's listed in the ExportedList_plugin.txt. Good to know.