[Interest] Build Qt from source in 32bit (-platform macx-clang-32)

[Nuno Santos]

> 
> On 28 May 2015, at 09:47, René J.V. Bertin <rjvbertin at gmail.com> wrote:
> 
> 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 ?

now! :) Sorry… typo!

> 
>> 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?

Sorry about my ignorance. what is the payload?

> 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.

I’m a baby boy regarding libraries, plugins and specially about the details of each platform. This is not something I deal on a daily basis so the learn curve tends to be quite hard.

I’m not sure if I can reply explicitly answer to your questions. The only thing I know so far is that if I build the bundle as 64 bit, run macdeploy on it and load it on a 64 bit host program, it behaves the same way, so I assume this is not an issue related with the 32 bit build. 

I can also observe that the bundle does load, if I don’t run macdeployqt on it. But i’m also sure that it won’t open on another computer without Qt installed on the same path. 

Is macdeployqt a recommended procedure for bundles? Or this is definitely not related?  

> 
> R.

Thanks,

Regards,

Nuno

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20150528/60a4065c/attachment.html>