App bundle immediately exits on MacOS #3884

Timmmm · 2020-12-08T20:38:46Z

Timmmm
Dec 8, 2020

I followed these instructions and end up with the following files (I didn't build the plugins yet):

$ exa --tree SQLiteStudio 
SQLiteStudio
├── libcoreSQLiteStudio.1.0.0.dylib
├── libcoreSQLiteStudio.1.0.dylib -> libcoreSQLiteStudio.1.0.0.dylib
├── libcoreSQLiteStudio.1.dylib -> libcoreSQLiteStudio.1.0.0.dylib
├── libcoreSQLiteStudio.dylib
├── libguiSQLiteStudio.1.0.0.dylib
├── libguiSQLiteStudio.1.0.dylib -> libguiSQLiteStudio.1.0.0.dylib
├── libguiSQLiteStudio.1.dylib -> libguiSQLiteStudio.1.0.0.dylib
├── libguiSQLiteStudio.dylib -> libguiSQLiteStudio.1.0.0.dylib
├── SQLiteStudio.app
│  └── Contents
│     ├── Info.plist
│     ├── MacOS
│     │  └── SQLiteStudio
│     ├── PkgInfo
│     └── Resources
│        ├── empty.lproj
│        └── sqlitestudio.icns
└── sqlitestudiocli

If I do this it runs correctly:

$ cd SQLiteStudio
$ cp ../../../lib/libsqlite3.dylib .
$ SQLiteStudio.app/Contents/MacOS/SQLiteStudio

However if try to run the app bundle it fails:

$ open SQLiteStudio.app
LSOpenURLsWithRole() failed with error -10810 for the file /Users/me/workspace/sqlitestudio/sqlitestudio/output/SQLiteStudio/SQLiteStudio.app.

So I tried running make bundle from output/build:

make bundle
sh /Users/me/workspace/sqlitestudio/sqlitestudio/SQLiteStudio3/create_macosx_bundle.sh /Users/me/workspace/sqlitestudio/sqlitestudio/SQLiteStudio3/../output /Users/me/Qt/5.15.2/clang_64/bin/qmake
cp: plugins: No such file or directory
mv: rename SQLiteStudio.app/Contents/plugins to SQLiteStudio.app/Contents/PlugIns: No such file or directory
cp: styles/*: No such file or directory
ERROR: no file at "/usr/lib/libcoreSQLiteStudio.1.dylib"
Replacing Info.plist
New plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
        <key>NSPrincipalClass</key>
        <string>NSApplication</string>
        <key>CFBundleIconFile</key>
        <string>sqlitestudio.icns</string>
        <key>CFBundlePackageType</key>
        <string>APPL</string>
        <key>CFBundleGetInfoString</key>
        <string>SalSoft, 2020</string>
        <key>CFBundleSignature</key>
        <string>????</string>
        <key>CFBundleShortVersionString</key>
        <string>3.2.2</string>
        <key>CFBundleExecutable</key>
        <string>SQLiteStudio</string>
        <key>CFBundleIdentifier</key>
        <string>pl.com.salsoft.SQLiteStudio</string>
        <key>CFBundleDocumentTypes</key>
        <array>
            <dict>
                <key>CFBundleTypeExtensions</key>
                <array>
                    <string>db</string>
                    <string>sdb</string>
                    <string>sqlite</string>
                    <string>db3</string>
                    <string>s3db</string>
                    <string>sqlite3</string>
                    <string>sl3</string>
                    <string>db2</string>
                    <string>s2db</string>
                    <string>sqlite2</string>
                    <string>sl2</string>
                </array>
                <key>CFBundleTypeName</key>
                <string>SQLite Database Document</string>
                <key>CFBundleTypeOSTypes</key>
                <array>
                    <string>****</string>
                </array>
                <key>CFBundleTypeRole</key>
                <string>Editor</string>
            </dict>
        </array>
    </dict>
</plist>

(See #3881 for the ERROR: no file at "/usr/lib/libcoreSQLiteStudio.1.dylib" error)

It did copy a load of files into the .app but now when I run it it just immediately exits. No error messages or anything.

Timmmm · 2020-12-08T20:40:18Z

Timmmm
Dec 8, 2020
Author

Hmm actually I think this might be caused by #3881 - the "Console" app has this crash report:

Termination Reason:    DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: libcoreSQLiteStudio.1.dylib
  Referenced from: /Users/USER/*/SQLiteStudio.app/Contents/MacOS/SQLiteStudio
  Reason: image not found

0 replies

Timmmm · 2020-12-08T20:42:11Z

Timmmm
Dec 8, 2020
Author

But it is in the bundle... I have no idea what is going on now...

.
├── libcoreSQLiteStudio.1.0.0.dylib
├── libcoreSQLiteStudio.1.0.dylib -> libcoreSQLiteStudio.1.0.0.dylib
├── libcoreSQLiteStudio.1.dylib -> libcoreSQLiteStudio.1.0.0.dylib
├── libcoreSQLiteStudio.dylib
├── libguiSQLiteStudio.1.0.0.dylib
├── libguiSQLiteStudio.1.0.dylib -> libguiSQLiteStudio.1.0.0.dylib
├── libguiSQLiteStudio.1.dylib -> libguiSQLiteStudio.1.0.0.dylib
├── libguiSQLiteStudio.dylib -> libguiSQLiteStudio.1.0.0.dylib
├── libsqlite3.dylib
├── SQLiteStudio.app
│  └── Contents
│     ├── Frameworks
│     │  ├── libcoreSQLiteStudio.1.0.0.dylib
│     │  ├── libcoreSQLiteStudio.1.0.dylib -> libcoreSQLiteStudio.1.0.0.dylib
│     │  ├── libcoreSQLiteStudio.1.dylib -> libcoreSQLiteStudio.1.0.0.dylib
│     │  ├── libcoreSQLiteStudio.dylib
│     │  ├── libguiSQLiteStudio.1.0.0.dylib
│     │  ├── libguiSQLiteStudio.1.0.dylib -> libguiSQLiteStudio.1.0.0.dylib
│     │  ├── libguiSQLiteStudio.1.dylib
│     │  ├── libguiSQLiteStudio.dylib -> libguiSQLiteStudio.1.0.0.dylib
│     │  ├── libsqlite3.dylib
...

0 replies

Timmmm · 2020-12-08T20:44:23Z

Timmmm
Dec 8, 2020
Author

Ah sorry ignore the previous two messages - this is the real problem:

Dec  8 20:43:02 me-laptop SQLiteStudio[17374]: dyld: lazy symbol binding failed: Symbol not found: _sqlite3_enable_load_extension
	  Referenced from: /Users/me/workspace/sqlitestudio/sqlitestudio/output/SQLiteStudio/SQLiteStudio.app/Contents/MacOS/../Frameworks/libcoreSQLiteStudio.1.dylib
	  Expected in: /usr/lib/libsqlite3.dylib
Dec  8 20:43:02 me-laptop SQLiteStudio[17374]: dyld: Symbol not found: _sqlite3_enable_load_extension
	  Referenced from: /Users/me/workspace/sqlitestudio/sqlitestudio/output/SQLiteStudio/SQLiteStudio.app/Contents/MacOS/../Frameworks/libcoreSQLiteStudio.1.dylib
	  Expected in: /usr/lib/libsqlite3.dylib

Somehow it is still looking for libsqlite3.dylib in the system version. This would be a whole lot easier if SQLite3 were bundled and statically compiled!

0 replies

Timmmm · 2020-12-08T21:41:36Z

Timmmm
Dec 8, 2020
Author

Aha well I figured it out. So I just naively compiled my copy of SQLite in the normal clang -shared ... way, which gives it an install name of libsqlite3.dylib:

$ otool -L libsqlite3.dylib 
libsqlite3.dylib:
        libsqlite3.dylib (compatibility version 0.0.0, current version 0.0.0)  <-- This is the install name I think.
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1292.0.0)

That gets copied to libcoreSQLiteStudio.1.dylib as the name of the library to look for:

$ otool -L libcoreSQLiteStudio.1.dylib
libcoreSQLiteStudio.1.dylib:
        libcoreSQLiteStudio.1.dylib (compatibility version 1.0.0, current version 1.0.0)
        libsqlite3.dylib (compatibility version 0.0.0, current version 0.0.0) <-- It gets copied here.
        @rpath/QtScript.framework/Versions/5/QtScript (compatibility version 5.15.0, current version 5.15.2)
        @rpath/QtNetwork.framework/Versions/5/QtNetwork (compatibility version 5.15.0, current version 5.15.2)
...

However because it doesn't have a @rpath prefix it doesn't look in the RPATH (which is set to something like ., .../Frameworks), and therefore finds it in /usr/lib instead.

We can fix it with install_name_tool, everyone's favourite undocumented tool.

$ install_name_tool -id @rpath/libsqlite3.dylib libsqlite3.dylib
$ otool -L libsqlite3.dylib                                     
libsqlite3.dylib:
        @rpath/libsqlite3.dylib (compatibility version 0.0.0, current version 0.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1292.0.0)

After doing that, and then a clean build it works! I will update the wiki with instructions. Again I can't stress enough how much easier this would have been if SQLite were just bundled by default.

0 replies

pawelsalawa · 2020-12-09T11:51:58Z

pawelsalawa
Dec 9, 2020
Maintainer

The problem with boundled SQLite is that it makes it impossible to replace it during runtime with another binary (if anyone downloaded precompiled binary). It helped many people already, as they were able to replace SQLite with newer release and use its features, without waiting for SQLiteStudio release.

I'm not sure why did you go through all of these compilation problems if you could just download a precompiled binary? Unless you wish to contribute (in which case I'm very happy).

0 replies

pawelsalawa · 2020-12-09T11:52:38Z

pawelsalawa
Dec 9, 2020
Maintainer

I'll convert this to the GitHub Discussions item now.

0 replies

Timmmm · 2020-12-09T14:31:01Z

Timmmm
Dec 9, 2020
Author

Unless you wish to contribute (in which case I'm very happy).

Exactly! :-)

1 reply

pawelsalawa Dec 10, 2020
Maintainer

That's great! I'm happy to assist. I don't have enough time to do a regular development (I do a little from time to time), but I'm happy to provide answers and hints.

Please be aware that the master branch is not very stable at the moment. Last time I worked with it I did quite significant change regarding translation files (so that the CrowdIn platform could be integrated) and I think I didn't finalize it. I still need to do some cleanups on this.

Second thing is that CI pipeline (GitHub Actions) are currently broken and builds will fail. It doesn't take much to fix them, so hopefully I'll fix them sooner than later.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

App bundle immediately exits on MacOS #3884

{{title}}

Replies: 7 comments 1 reply

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

App bundle immediately exits on MacOS #3884

Timmmm Dec 8, 2020

Replies: 7 comments · 1 reply

Timmmm Dec 8, 2020 Author

Timmmm Dec 8, 2020 Author

Timmmm Dec 8, 2020 Author

Timmmm Dec 8, 2020 Author

pawelsalawa Dec 9, 2020 Maintainer

pawelsalawa Dec 9, 2020 Maintainer

Timmmm Dec 9, 2020 Author

pawelsalawa Dec 10, 2020 Maintainer

Timmmm
Dec 8, 2020

Replies: 7 comments 1 reply

Timmmm
Dec 8, 2020
Author

Timmmm
Dec 8, 2020
Author

Timmmm
Dec 8, 2020
Author

Timmmm
Dec 8, 2020
Author

pawelsalawa
Dec 9, 2020
Maintainer

pawelsalawa
Dec 9, 2020
Maintainer

Timmmm
Dec 9, 2020
Author

pawelsalawa Dec 10, 2020
Maintainer