Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. OSX - shared/static libs conflict
QtWS25 Last Chance

OSX - shared/static libs conflict

Scheduled Pinned Locked Moved Installation and Deployment
2 Posts 2 Posters 1.8k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    rivierakid
    wrote on last edited by
    #1

    Hi,

    I'm developing a shared library which uses the Qt4 static library. I would like to use this library from an application that also internally uses Qt4 (dynamic). There is no problem in Win32, but in OSX there is a library conflict and my shared library can't be called from the main application becuase of 2 versions of Qt (one shared and one statically linked).

    The main app is Foundry Nuke and Qt version is 4.6.2
    My plugin (shared library) uses Qt 4.8.0

    OSX - Is there any way to use two Qt-libs (dynamic and static) in the same process? Because no problem in Win32...

    Thanks
    Martin

    1 Reply Last reply
    0
    • R Offline
      R Offline
      rcari
      wrote on last edited by
      #2

      My first guess would be to say that you can't do that on OS X.
      You should make Foundry Nuke use the newest version of Qt (4.8.0) by using otool to change its Qt dylib dependencies, or use Qt 4.6.2 in your plugin.

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved