Date
1 - 3 of 3
link problem with Visual Studio 2012
Jeremy Selan <jeremy...@...>
Are you using the proper generated headers? Are you overriding so version in CMake? All the symbols are in OpenColorIO::v0, and I would expect them to be in v1 (corresponding to the major version). #define OCIO_NAMESPACE_ENTER namespace OCIO_NAMESPACE { namespace OCIO_VERSION_NS
set(OCIO_VERSION_MAJOR 1) set(OCIO_VERSION_MINOR 0) set(OCIO_VERSION_PATCH 9) set(SOVERSION ${OCIO_VERSION_MAJOR} CACHE STRING "Set the SO version in the SO name of the output library") On Mon, Dec 5, 2016 at 10:24 AM, Paul Miller <pa...@...> wrote: I'm in the twilight zone today. After a bad merge from Mac->Windows, my application will no longer link against the shared OpenColorIO.lib on Windows, using Visual Studio 2012. This is the exact same set of headers and .lib I've been using for over a year. |
||
|
||
Dithermaster <dither...@...>
Is this 32-bit or 64-bit? If 32-bit, did you change the default calling convention in your project (__cdecl vs __stdcall)? Undecorated headers with .lib files that use the default convention will fail if you've changed the default convention. In 64-bit this is moot since it's all __fastcall. On Mon, Dec 5, 2016 at 12:42 PM, Jeremy Selan <jeremy...@...> wrote:
|
||
|
||
Paul Miller <pa...@...>
On 12/5/2016 4:12 PM, Dithermaster wrote:
Is this 32-bit or 64-bit? If 32-bit, did you change the default callingNo, 64 bit only. I used the default cmake settings, though I did run cmake and build with cygwin in my path (so "patch" would work when building tinyxml). I'll look into the v0 vs v1 issue - that looks like it may be the culprit.
|
||
|