I wish this helpful for you After much searching, I finally stumbled across Richard Lord's excellent blog post on AIR native extensions. It turns out that effective development requires use of a few flags that Adobe hasn't bothered to document yet (unless you count developer blog posts as documentation -- I don't). Long story short:
How to build executable with all library dependencies included for NetBeans?
I wish this help you There's the nm command. It lists the modules functions. Runs the nm command and grep a function you know is in the lib/so. If it's dynamically linked (so library) you'll see a "U" attribute to it. Example (perl path is made up):
nm /bin/perl | grep fprintf
I receive different results on UNIX and WIN when use static members with static linking of shared library to executable.
around this issue In windows, A DLL is not exporting global and static symbols unless you add the dllexport statement, therefore, the linker doesn't even know they exists, so it allocate new instance for the static member. In linux/unix a shared lib is exporting all the global and static symbols, so when the linker find the existence of the static member in the shared lib, it just use its address.
How to force symbols from a static library to be included in a shared library build?