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

[Nuno Santos]

I’m an idiot…

I didn’t build tools, as you can see in my configure line. This is because that configure line was originally made for a static build on windows, were I don’t need tools such as windeployqt.

However in Mac, I can deploy everything in a bundle, so there is no need for a static build. In this case macdeployqt is useful. 

What I did was to use the clang_64 macdeployqt because i’m really used to call it and it was automatically typed by my fingers. I didn’t even think twice. That’s why the frameworks were 64 bit builds. 

I have built tools and run the proper macdeployqt. Frameworks are not i386 arch. However, the plugin is still not loaded but the host. It is giving this error:

2015-05-28 08:13:02.022 Live[29289:526979] Error loading /Users/nsantos/workspace/drc/vstbuild/32/audiolab.vst/Contents/MacOS/audiolab:  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
2015-05-28 08:13:02.024 Live[29289:526979] Error loading /Users/nsantos/workspace/drc/vstbuild/32/audiolab.vst/Contents/MacOS/audiolab:  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

However, the QtQuick.framework is in the frameworks directory. Is there any possibility of any QtQuick dependency is failing? How can one know more about the reason of the failure in such case?

Thanks,

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

> On 28 May 2015, at 07:32, Nuno Santos <nunosantos at imaginando.pt> wrote:
> 
> This is the qmake.stash file content. I can’t find anything mean-full here. Does this rings you any bell?
> 
> QMAKE_XCODE_DEVELOPER_PATH = /Applications/Xcode.app/Contents/Developer
> QMAKE_XCODE_VERSION = 6.3.2
> QMAKE_MAC_SDK.macosx.path = /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk
> QMAKE_MAC_SDK.macosx.version = 10.10
> QMAKE_MAC_SDK.macx-clang-32.macosx.QMAKE_CC = /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
> QMAKE_MAC_SDK.macx-clang-32.macosx.QMAKE_CXX = /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
> QMAKE_MAC_SDK.macx-clang-32.macosx.QMAKE_FIX_RPATH = \
>    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool \
>    -id
> QMAKE_MAC_SDK.macx-clang-32.macosx.QMAKE_AR = \
>    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ar \
>    cq
> QMAKE_MAC_SDK.macx-clang-32.macosx.QMAKE_RANLIB = \
>    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib \
>    -s
> QMAKE_MAC_SDK.macx-clang-32.macosx.QMAKE_LINK = /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
> QMAKE_MAC_SDK.macx-clang-32.macosx.QMAKE_LINK_SHLIB = /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
> QMAKE_MAC_SDK.macosx.platform_name = macosx
> 
> 
> 
>> On 28/05/2015, at 02:55, René J.V. Bertin <rjvbertin at gmail.com> wrote:
>> 
>> On Wednesday May 27 2015 23:37:34 Nuno Santos wrote:
>>> Thanks Thiago
>>> 
>>> I always delete the source folder and start with a new one when configuration changes drastically. I have built Qt from a clean source dir.
>>> 
>>> Maybe something is missing in the configure line then?
>>> 
>>> configure -prefix /Users/nsantos/Qt/5.4/clang_32 -platform macx-clang-32 -commercial -release -nomake examples -nomake tools -nomake tests -opengl desktop -skip webkit -skip multimedia
>>> 
>>> Does anyone has a clue?
>> 
>> Hi,
>> 
>> I had some issues a while back trying to write a MacPorts "recipe" to create a universal 32+64 bit build. I cannot remember the details at the moment, but I managed to work around them by copying a corrected version of .qmake.stash to ${build.dir}/qtbase and ${build.dir} *before* running configure.
>> 
>> So have a look at the .qmake.stash files you have now after running configure, maybe that teaches you something.
>> 
>> R.
> 
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

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