OS X - Designer cannot be opened because of a problem

SGaist

Is it really the Designer app that comes with the Qt 5.4 SDK ?

nbro

@SGaist The following is my current directory: /Users/cell/Qt/5.4/clang_64/bin, and if I Iist it using ls:

Assistant.app
Designer.app
Linguist.app
QMLViewer.app
lconvert
lrelease
lupdate
macchangeqt
macdeployqt
moc
pixeltool.app
qcollectiongenerator
qdbus
qdbuscpp2xml
qdbusviewer.app
qdbusxml2cpp
qdoc
qhelpconverter
qhelpgenerator
qlalr
qmake
qml.app
qml1plugindump
qml2puppet.app
qmlbundle
qmleasing
qmlimportscanner
qmllint
qmlmin
qmlplugindump
qmlprofiler
qmlscene
qmltestrunner
qt.conf
qtdiag
qtpaths
rcc
syncqt.pl
uic
xmlpatterns
xmlpatternsvalidator

Now, if I output the contents of Designer.app:

Designer.app/
└── Contents
    ├── Info.plist
    ├── MacOS
    │   └── Designer
    ├── PkgInfo
    └── Resources
        ├── designer.icns
        ├── empty.lproj
        └── uifile.icns

3 directories, 6 files

If I try to run the executable Designer, I get the following error, which seems to be the same as the one in the crash, that is the miss of libQtDesignerComponents.4.dylib

dyld: Library not loaded: @loader_path/../../../../lib/libQtDesignerComponents.4.dylib
  Referenced from: /Users/cell/Qt/5.4/clang_64/bin/Designer.app/Contents/MacOS/./Designer
  Reason: image not found
Trace/BPT trap: 5

SGaist

What do you get if your run otool -L Designer ?

nbro

@SGaist said:

otool -L Designer

Designer:
	@loader_path/../../../../lib/libQtDesignerComponents.4.dylib (compatibility version 4.8.0, current version 4.8.6)
	@loader_path/../../../../lib/libQtDesigner.4.dylib (compatibility version 4.8.0, current version 4.8.6)
	@loader_path/../../../../lib/libQtScript.4.dylib (compatibility version 4.8.0, current version 4.8.6)
	@loader_path/../../../../lib/libQtXml.4.dylib (compatibility version 4.8.0, current version 4.8.6)
	@loader_path/../../../../lib/libQtGui.4.dylib (compatibility version 4.8.0, current version 4.8.6)
	@loader_path/../../../../lib/libQtNetwork.4.dylib (compatibility version 4.8.0, current version 4.8.6)
	@loader_path/../../../../lib/libQtCore.4.dylib (compatibility version 4.8.0, current version 4.8.6)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0)
	/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1094.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)

SGaist

That's a Qt 4 version of Designer, not a 5.4

nbro

@SGaist But why do I have the version 4 of Qt Designer inside the folder of Qt 5.4?

SGaist

Well, that I don't know, but it's clearly not the right version of Designer. Did you use brew to install stuff ?

nbro

@SGaist I have closed the terminal and opened it again and run your command again, but now I have the following output:

error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/otool: can't open file: Designer (No such file or directory)

nbro

@SGaist Also, I think this cannot be a problem related to the version of Designer, since I can use it normally from Qt Creator.

SGaist

Since you closed the terminal you first have to go again in the folder where Designer is located

Qt Creator has a designer plugin which is not the same thing as the Designer application

nbro

@SGaist Yes, and I am having the same output, which seems that the standalone Designer.app that comes with my Qt 5.4 distribution is for Qt 4.8, which is really strange.

I am not sure if I had used brew to install something, but running brew list does not show apparently any packages or programs related to Qt:

clang-format
cmake
cscope
dmd
dub
freetype
gdbm
jpeg
libpng
libtiff
little-cms
mercurial
openssl
pcre
pkg-config
portmidi
sdl
sdl2
sdl_image
sdl_mixer
sdl_ttf
tree
webp
wget
zsh

SGaist

That really strange…

The output of brew list doesn't seem suspicious

I just verified with 5.5 and it's all ok

nbro

At the end, I decided to uninstall Qt 5.4 (using the MaintenanceTool that comes with the program) and install Qt 5.5. For now, the Designer.app works normally.

I have also reinstalled PyQt5 globally instead of on a virtualenv. I have had some problems related to licenses' compatibility, that I solved by commenting 2 statements in the configure.py of PyQt5, before building. This pseudo solution to this problem can be found on the web.

SGaist

There must have a been a strange glitch at some point somewhere...