Note that there are some explanatory texts on larger screens.

plurals
  1. POQt .nib issues on MacOS
    primarykey
    data
    text
    <p>I'm trying to deploy a Qt C++ application on another mac that doesn't have Qt installed. I am getting a "Qt internal error: qt_menu.nib could not be loaded. The .nib file should be placed in QtGui.framework/Versions/Current/Resources/ or in the resources directory of your application bundle."</p> <p>I've tried packing qt_menu.lib into both suggested places, with no success:</p> <pre><code>$ ls ./arya.app/Resources/ qt_menu.nib $ ./arya.app/Contents/MacOS/arya Qt internal error: qt_menu.nib could not be loaded. The .nib file should be placed in QtGui.framework/Versions/Current/Resources/ or in the resources directory of your application bundle. </code></pre> <p>or:</p> <pre><code>$ mkdir QtGui.framework $ mkdir QtGui.framework/Versions/ $ mkdir QtGui.framework/Versions/Current/ $ mkdir QtGui.framework/Versions/Current/Resources $ mv ./arya.app/Resources/qt_menu.nib QtGui.framework/Versions/Current/Resources/ $ ./arya.app/Contents/MacOS/arya Qt internal error: qt_menu.nib could not be loaded. The .nib file should be placed in QtGui.framework/Versions/Current/Resources/ or in the resources directory of your application bundle. </code></pre> <p>I'm not sure if there may be some connection, but I had some issues with dylib paths before this. After stumbling about with install_name_tool, I 'solved' them with:</p> <pre><code>export DYLD_LIBRARY_PATH=. </code></pre> <p>before running the application.</p> <p>Building the application with</p> <pre><code>CONFIG -= app_bundle </code></pre> <p>made no difference.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload