On Thursday May 28 2015 08:19:07 Nuno Santos wrote: >I’m an idiot…
Just your fingers, apparently. I'm increasingly coming to that conclusion about my own digits too ;) (Maybe you should try using 2 less, or align with computing practices... ^^) >I have built tools and run the proper macdeployqt. Frameworks are not i386 >arch. ^not^now ? >dlopen(/Users/nsantos/workspace/drc/vstbuild/32/audiolab.vst/Contents/MacOS/audiolab, > 262): >Library not loaded: >@executable_path/../Frameworks/QtQuick.framework/Versions/5/QtQuick > Referenced from: > /Users/nsantos/workspace/drc/vstbuild/32/audiolab.vst/Contents/MacOS/audiolab > Reason: image not found Stupid question: you did check that not only is the framework bundle there, its payload is there too exactly as shown? Also, what type is that binary? Dyld prints a rather explicit, detailed message when it fails to find an appropriate shared library, but I'm not sure dlopen does the same thing. You probably know that OS X has a distinction between shared libraries/frameworks and "bundles", inappropriately chosen term for plugins that can be built with transparent/automatic access to the host app's symbols and can not be used as shared libraries (but only through dlopen). Traditional libraries/frameworks can be used as plugins (through dlopen) though. Those plugin bundles usually don't get the framework form though, so if you used Qt's build system and you're using QtQuick as a plugin the way it's intended, I must be talking out of my neck here. R. _______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
