You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ogre2 and ogre22 vcpkg formulas in this repository relocate the installation directory so they can co-installed with the official ogre 1.x formula in vcpkg. The dlls are placed under vcpkg/installed/$arch-triplet/bin/OGRE-2.2 which is a directory added to the PATH when vcpkg integrate install is being run.
The DLL of the Ogre 1.x and Ogre2/Ogre22 have exactly the same name, this has probably the effect of the loader to load Ogre 1.x DLL when a binary uses Ogre 2.x or Ogre 1.x.
This problem did not happen in Linux since the .so binary files (not the symlink) have the different version ABI identifiers as part of the file extension.
The text was updated successfully, but these errors were encountered:
The ogre2 and ogre22 vcpkg formulas in this repository relocate the installation directory so they can co-installed with the official ogre 1.x formula in vcpkg. The dlls are placed under
vcpkg/installed/$arch-triplet/bin/OGRE-2.2which is a directory added to thePATHwhenvcpkg integrate installis being run.The DLL of the Ogre 1.x and Ogre2/Ogre22 have exactly the same name, this has probably the effect of the loader to load Ogre 1.x DLL when a binary uses Ogre 2.x or Ogre 1.x.
This problem did not happen in Linux since the .so binary files (not the symlink) have the different version ABI identifiers as part of the file extension.
The text was updated successfully, but these errors were encountered: