OS X - Designer cannot be opened because of a problem

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