[digikam] [Bug 366202] New: Bootstrap script does not test for QT5 mysql library

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366202

            Bug ID: 366202
           Summary: Bootstrap script does not test for QT5 mysql library
           Product: digikam
           Version: 5.1.0
          Platform: Debian testing
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: setup
          Assignee: [hidden email]
          Reporter: [hidden email]

I am trying to setup digiKam with internal Mysql database. I am running into
several bugs and am currently fixing them (more on this later). The following
error occured during initialisation:
    QSqlDatabase: QMYSQL driver not loaded
    QSqlDatabase: available drivers: QSQLITE
    digikam.databaseserver: Invalid database object during database server
startup
I checked and I was missing the file libqsqlmysql.so. On debian this file is
included in package "libqt5sql5-mysql" and located in:
    /usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/
The bootstrap script did not report an error or warning (internal mysql was
obviously enabled). but it should.

Reproducible: Always

Steps to Reproduce:
1. Run bootstrap.linux without having libqsqlmysql.so installed


Actual Results:  
Script reports success.

Expected Results:  
Script should report failure and state that it did not find the necessary
libraries.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366202

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Bootstrap script does not   |Cmake script does not test
                   |test for QT5 mysql library  |for QT5 mysql module
                   |                            |availability
          Component|setup                       |Portability
                 CC|                            |[hidden email]

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366202

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|5.1.0                       |5.0.0

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366202

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from [hidden email] ---
The QtQQL driver availability is only tested at run time by Qt5 when digiKAm
startup.

If relevant QtSql driver is missing, just install it. digiKam will report the
error in a dialog at startup.

The bootstrap script will only check if components are present to compile
source code, not to run it. This is a non sense to check QtSql driver before
compilation time.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366202

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Portability                 |Bundle-Tarball

--
You are receiving this mail because:
You are the assignee for the bug.