First off, sorry if I misplaced this. It isn't directly game-programming related but since the offending library sort-of is I eventually settled on this forum.
(Edit: now that I think about it that motivation makes zero sense. Oh well, let's blame tiredness instead then :rolleyes: )
So I migrated my game engine from VS2010 to 2013 a few months back and got everything to run as intended with some rebuilt dependencies. However I recently noticed that my projects ends up exporting symbols for the Assimp library. This is a static library I've built myself to use the VS2013 platform toolset and is based on the Assimp 1.6.0 source. My question is why this is happening and what I can do to avoid it?
My guess would be that there is some compiler setting I have to specify when building the Assimb library (I am referencing several other static libraries that doesn't drag along all of their internal exports after all) but I'm lost as to which one. None of the functions in that library has any particular declspec or similar either.
Any suggestions on what to do about this?