New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Patch hardcoded absolute qt_ paths #79

Closed
probonopd opened this Issue Feb 20, 2017 · 12 comments

Comments

Projects
None yet
2 participants
@probonopd
Owner

probonopd commented Feb 20, 2017

This ticket does not affect Qt builds from the beineri ppas, which I recommend for building on Travis CI (verified with Qt 5.8 for trusty from the ppa).

strings libQt5Core.so.5 | grep qt_ | grep = | cut -d "=" -f 1 reveals on a distribution-provided libQt5Core (Qt 5.2 from Ubuntu trusty repository) that there are many hardcoded absolute paths that we may need to change:

  • qt_stngpath
  • qt_prfxpath
  • qt_docspath
  • qt_hdrspath
  • qt_libspath
  • qt_lbexpath
  • qt_binspath
  • qt_plugpath
  • qt_impspath
  • qt_qml2path
  • qt_adatpath
  • qt_datapath
  • qt_trnspath
  • qt_xmplpath
  • qt_tstspath
@probonopd

This comment has been minimized.

Show comment
Hide comment
@probonopd

probonopd Mar 2, 2017

Owner

According to https://patchwork.openembedded.org/patch/87519/ there is even more:

+-    "qt_prfxpath=$QT_INSTALL_PREFIX",
+-    "qt_docspath=$QT_INSTALL_DOCS",
+-    "qt_hdrspath=$QT_INSTALL_HEADERS",
+-    "qt_libspath=$QT_INSTALL_LIBS",
+-    "qt_lbexpath=$QT_INSTALL_LIBEXECS",
+-    "qt_binspath=$QT_INSTALL_BINS",
+-    "qt_plugpath=$QT_INSTALL_PLUGINS",
+-    "qt_impspath=$QT_INSTALL_IMPORTS",
+-    "qt_qml2path=$QT_INSTALL_QML",
+-    "qt_adatpath=$QT_INSTALL_ARCHDATA",
+-    "qt_datapath=$QT_INSTALL_DATA",
+-    "qt_trnspath=$QT_INSTALL_TRANSLATIONS",
+-    "qt_xmplpath=$QT_INSTALL_EXAMPLES",
+-    "qt_tstspath=$QT_INSTALL_TESTS",
+-    "qt_ssrtpath=$CFG_SYSROOT",
+-    "qt_hpfxpath=$QT_HOST_PREFIX",
+-    "qt_hbinpath=$QT_HOST_BINS",
+-    "qt_hlibpath=$QT_HOST_LIBS",
+-    "qt_hdatpath=$QT_HOST_DATA",
+-    "qt_ebinpath=$QT_EXTERNAL_HOST_BINS",
+-    "qt_targspec=$shortxspec",
+-    "qt_hostspec=$shortspec",
++    "qt_prfxpath=$QT_SYSROOT_PREFIX",
++    "qt_docspath=$QT_SYSROOT_DOCS",
++    "qt_hdrspath=$QT_SYSROOT_HEADERS",
++    "qt_libspath=$QT_SYSROOT_LIBS",
++    "qt_lbexpath=$QT_SYSROOT_LIBEXECS",
++    "qt_binspath=$QT_SYSROOT_BINS",
++    "qt_plugpath=$QT_SYSROOT_PLUGINS",
++    "qt_impspath=$QT_SYSROOT_IMPORTS",
++    "qt_qml2path=$QT_SYSROOT_QML",
++    "qt_adatpath=$QT_SYSROOT_ARCHDATA",
++    "qt_datapath=$QT_SYSROOT_DATA",
++    "qt_trnspath=$QT_SYSROOT_TRANSLATIONS",
++    "qt_xmplpath=$QT_SYSROOT_EXAMPLES",
++    "qt_tstspath=$QT_SYSROOT_TESTS",
++    "qt_ssrtpath=",
++    "qt_hpfxpath=$QT_SYSROOT_PREFIX",
++    "qt_hbinpath=$QT_SYSROOT_BINS",
++    "qt_hlibpath=$QT_SYSROOT_LIBS",
++    "qt_hdatpath=$QT_SYSROOT_LIBS/qt5",
++    "qt_targspec=linux-g++",
++    "qt_hostspec=linux-g++",

Is this documented somewhere?

Owner

probonopd commented Mar 2, 2017

According to https://patchwork.openembedded.org/patch/87519/ there is even more:

+-    "qt_prfxpath=$QT_INSTALL_PREFIX",
+-    "qt_docspath=$QT_INSTALL_DOCS",
+-    "qt_hdrspath=$QT_INSTALL_HEADERS",
+-    "qt_libspath=$QT_INSTALL_LIBS",
+-    "qt_lbexpath=$QT_INSTALL_LIBEXECS",
+-    "qt_binspath=$QT_INSTALL_BINS",
+-    "qt_plugpath=$QT_INSTALL_PLUGINS",
+-    "qt_impspath=$QT_INSTALL_IMPORTS",
+-    "qt_qml2path=$QT_INSTALL_QML",
+-    "qt_adatpath=$QT_INSTALL_ARCHDATA",
+-    "qt_datapath=$QT_INSTALL_DATA",
+-    "qt_trnspath=$QT_INSTALL_TRANSLATIONS",
+-    "qt_xmplpath=$QT_INSTALL_EXAMPLES",
+-    "qt_tstspath=$QT_INSTALL_TESTS",
+-    "qt_ssrtpath=$CFG_SYSROOT",
+-    "qt_hpfxpath=$QT_HOST_PREFIX",
+-    "qt_hbinpath=$QT_HOST_BINS",
+-    "qt_hlibpath=$QT_HOST_LIBS",
+-    "qt_hdatpath=$QT_HOST_DATA",
+-    "qt_ebinpath=$QT_EXTERNAL_HOST_BINS",
+-    "qt_targspec=$shortxspec",
+-    "qt_hostspec=$shortspec",
++    "qt_prfxpath=$QT_SYSROOT_PREFIX",
++    "qt_docspath=$QT_SYSROOT_DOCS",
++    "qt_hdrspath=$QT_SYSROOT_HEADERS",
++    "qt_libspath=$QT_SYSROOT_LIBS",
++    "qt_lbexpath=$QT_SYSROOT_LIBEXECS",
++    "qt_binspath=$QT_SYSROOT_BINS",
++    "qt_plugpath=$QT_SYSROOT_PLUGINS",
++    "qt_impspath=$QT_SYSROOT_IMPORTS",
++    "qt_qml2path=$QT_SYSROOT_QML",
++    "qt_adatpath=$QT_SYSROOT_ARCHDATA",
++    "qt_datapath=$QT_SYSROOT_DATA",
++    "qt_trnspath=$QT_SYSROOT_TRANSLATIONS",
++    "qt_xmplpath=$QT_SYSROOT_EXAMPLES",
++    "qt_tstspath=$QT_SYSROOT_TESTS",
++    "qt_ssrtpath=",
++    "qt_hpfxpath=$QT_SYSROOT_PREFIX",
++    "qt_hbinpath=$QT_SYSROOT_BINS",
++    "qt_hlibpath=$QT_SYSROOT_LIBS",
++    "qt_hdatpath=$QT_SYSROOT_LIBS/qt5",
++    "qt_targspec=linux-g++",
++    "qt_hostspec=linux-g++",

Is this documented somewhere?

@carlos22

This comment has been minimized.

Show comment
Hide comment
@carlos22

carlos22 Mar 22, 2017

Archlinux:

> strings libQt5Core.so.5 | grep qt_ | grep = | cut -d "=" -f 1
qt_prfxpath
qt_instdate
> pacman -Qi qt5-base
Name                     : qt5-base
Version                  : 5.8.0-7
Beschreibung             : A cross-platform application and UI framework
Architektur              : x86_64

carlos22 commented Mar 22, 2017

Archlinux:

> strings libQt5Core.so.5 | grep qt_ | grep = | cut -d "=" -f 1
qt_prfxpath
qt_instdate
> pacman -Qi qt5-base
Name                     : qt5-base
Version                  : 5.8.0-7
Beschreibung             : A cross-platform application and UI framework
Architektur              : x86_64
@carlos22

This comment has been minimized.

Show comment
Hide comment
@carlos22

carlos22 Mar 24, 2017

Suggestion for some vars:

qt_prfxpath=.
qt_docspath=./doc
qt_hdrspath=./include
qt_libspath=./lib
qt_lbexpath=./libexec
qt_binspath=./bin
qt_plugpath=./plugins
qt_impspath=./imports
qt_qml2path=./qml
qt_adatpath=.
qt_datapath=.
qt_trnspath=./translations
qt_xmplpath=./examples
qt_tstspath=./tests

Based on: https://bugreports.qt.io/browse/QTBUG-31760

This seems to be the default: https://code.woboq.org/qt5/qtbase/src/corelib/global/qconfig.cpp.html#qt_configure_strs
The qconfig.cpp file is generated by qmake. The other definitions seem to be only relevant if qmake itself is build.

The only missing (based on the values from ubuntu) is qt_stngpath.

carlos22 commented Mar 24, 2017

Suggestion for some vars:

qt_prfxpath=.
qt_docspath=./doc
qt_hdrspath=./include
qt_libspath=./lib
qt_lbexpath=./libexec
qt_binspath=./bin
qt_plugpath=./plugins
qt_impspath=./imports
qt_qml2path=./qml
qt_adatpath=.
qt_datapath=.
qt_trnspath=./translations
qt_xmplpath=./examples
qt_tstspath=./tests

Based on: https://bugreports.qt.io/browse/QTBUG-31760

This seems to be the default: https://code.woboq.org/qt5/qtbase/src/corelib/global/qconfig.cpp.html#qt_configure_strs
The qconfig.cpp file is generated by qmake. The other definitions seem to be only relevant if qmake itself is build.

The only missing (based on the values from ubuntu) is qt_stngpath.

@carlos22

This comment has been minimized.

Show comment
Hide comment
@carlos22

carlos22 Mar 24, 2017

Qt Framework Installer

The Qt Installer Framework also patches the values, code is here: http://code.qt.io/cgit/installer-framework/installer-framework.git/tree/src/libs/installer/qtpatchoperation.cpp?id=0ff7968345752395af93334b174973ebefb95048#n106

It replaces qt_stngpath with the value of QT_INSTALL_CONFIGURATION

Get the value for your env:

> qmake -query "QT_INSTALL_CONFIGURATION"
/etc/xdg

Docs for the in the installer used replacements: http://doc.qt.io/qt-5/qmake-environment-reference.html

Strings handled by Qt Installer Framework:

qt_prfxpath
qt_adatpath
qt_docspath
qt_hdrspath
qt_libspath
qt_lbexpath
qt_binspath
qt_plugpath
qt_impspath
qt_qml2path
qt_datapath
qt_trnspath
qt_stngpath
qt_xmplpath
qt_demopath
qt_tstspath
qt_hpfxpath
qt_hbinpath
qt_hdatpath

Replacements for this values

QT_INSTALL_PREFIX
QT_INSTALL_ARCHDATA
QT_INSTALL_DOCS
QT_INSTALL_HEADERS
QT_INSTALL_LIBS
QT_INSTALL_LIBEXECS
QT_INSTALL_BINS
QT_INSTALL_PLUGINS
QT_INSTALL_IMPORTS
QT_INSTALL_QML
QT_INSTALL_DATA
QT_INSTALL_TRANSLATIONS
QT_INSTALL_CONFIGURATION
QT_INSTALL_EXAMPLES
QT_INSTALL_DEMOS
QT_INSTALL_TESTS
QT_HOST_PREFIX
QT_HOST_BINS
QT_HOST_DATA

values obtained with qmake -query <VAR> on my system

/usr
/usr/lib/qt
/usr/share/doc/qt
/usr/include/qt
/usr/lib
/usr/lib/qt/libexec
/usr/bin
/usr/lib/qt/plugins
/usr/lib/qt/imports
/usr/lib/qt/qml
/usr/share/qt
/usr/share/qt/translations
/etc/xdg
/usr/share/doc/qt/examples
/usr/share/doc/qt/examples
/usr/tests
/usr
/usr/bin
/usr/lib/qt

carlos22 commented Mar 24, 2017

Qt Framework Installer

The Qt Installer Framework also patches the values, code is here: http://code.qt.io/cgit/installer-framework/installer-framework.git/tree/src/libs/installer/qtpatchoperation.cpp?id=0ff7968345752395af93334b174973ebefb95048#n106

It replaces qt_stngpath with the value of QT_INSTALL_CONFIGURATION

Get the value for your env:

> qmake -query "QT_INSTALL_CONFIGURATION"
/etc/xdg

Docs for the in the installer used replacements: http://doc.qt.io/qt-5/qmake-environment-reference.html

Strings handled by Qt Installer Framework:

qt_prfxpath
qt_adatpath
qt_docspath
qt_hdrspath
qt_libspath
qt_lbexpath
qt_binspath
qt_plugpath
qt_impspath
qt_qml2path
qt_datapath
qt_trnspath
qt_stngpath
qt_xmplpath
qt_demopath
qt_tstspath
qt_hpfxpath
qt_hbinpath
qt_hdatpath

Replacements for this values

QT_INSTALL_PREFIX
QT_INSTALL_ARCHDATA
QT_INSTALL_DOCS
QT_INSTALL_HEADERS
QT_INSTALL_LIBS
QT_INSTALL_LIBEXECS
QT_INSTALL_BINS
QT_INSTALL_PLUGINS
QT_INSTALL_IMPORTS
QT_INSTALL_QML
QT_INSTALL_DATA
QT_INSTALL_TRANSLATIONS
QT_INSTALL_CONFIGURATION
QT_INSTALL_EXAMPLES
QT_INSTALL_DEMOS
QT_INSTALL_TESTS
QT_HOST_PREFIX
QT_HOST_BINS
QT_HOST_DATA

values obtained with qmake -query <VAR> on my system

/usr
/usr/lib/qt
/usr/share/doc/qt
/usr/include/qt
/usr/lib
/usr/lib/qt/libexec
/usr/bin
/usr/lib/qt/plugins
/usr/lib/qt/imports
/usr/lib/qt/qml
/usr/share/qt
/usr/share/qt/translations
/etc/xdg
/usr/share/doc/qt/examples
/usr/share/doc/qt/examples
/usr/tests
/usr
/usr/bin
/usr/lib/qt
@probonopd

This comment has been minimized.

Show comment
Hide comment
@probonopd

probonopd Mar 24, 2017

Owner

Awesome investigation @carlos22 - do I smell a PR coming?

Owner

probonopd commented Mar 24, 2017

Awesome investigation @carlos22 - do I smell a PR coming?

@probonopd

This comment has been minimized.

Show comment
Hide comment
@probonopd

probonopd Mar 26, 2017

Owner

When using https://launchpad.net/~beineri/+archive/ubuntu/opt-qt532-trusty then currently the following lands in the AppImage, which is clearly wrong:

[antergos@Antergos-ISO ~]$ strings squashfs-root/usr/lib/libQt5Core.so.5 | grep '^qt_.*='
qt_stngpath=/opt/qt53/etc/xdg
qt_prfxpath=..
qt_docspath=/opt/qt53/doc
qt_hdrspath=/opt/qt53/include
qt_libspath=/opt/qt53/lib
qt_lbexpath=/opt/qt53/libexec
qt_binspath=/opt/qt53/bin
qt_plugpath=plugins
qt_impspath=/opt/qt53/imports
qt_qml2path=/opt/qt53/qml
qt_adatpath=/opt/qt53
qt_datapath=/opt/qt53
qt_trnspath=/opt/qt53/translations
qt_xmplpath=/opt/qt53/examples
qt_tstspath=/opt/qt53/tests
qt_instdate=2015-03-11
qt_lcnsprod=OpenSource
qt_lcnsuser=Open Source
Owner

probonopd commented Mar 26, 2017

When using https://launchpad.net/~beineri/+archive/ubuntu/opt-qt532-trusty then currently the following lands in the AppImage, which is clearly wrong:

[antergos@Antergos-ISO ~]$ strings squashfs-root/usr/lib/libQt5Core.so.5 | grep '^qt_.*='
qt_stngpath=/opt/qt53/etc/xdg
qt_prfxpath=..
qt_docspath=/opt/qt53/doc
qt_hdrspath=/opt/qt53/include
qt_libspath=/opt/qt53/lib
qt_lbexpath=/opt/qt53/libexec
qt_binspath=/opt/qt53/bin
qt_plugpath=plugins
qt_impspath=/opt/qt53/imports
qt_qml2path=/opt/qt53/qml
qt_adatpath=/opt/qt53
qt_datapath=/opt/qt53
qt_trnspath=/opt/qt53/translations
qt_xmplpath=/opt/qt53/examples
qt_tstspath=/opt/qt53/tests
qt_instdate=2015-03-11
qt_lcnsprod=OpenSource
qt_lcnsuser=Open Source
@probonopd

This comment has been minimized.

Show comment
Hide comment
@probonopd

probonopd Mar 26, 2017

Owner

Check out QtBinPatcher source code from
http://repo.msys2.org/mingw/sources/mingw-w64-i686-qtbinpatcher-2.2.0-1.src.tar.gz
especially around here:

    static const TParam Params[] = {
        { "QT_INSTALL_PREFIX",       "qt_prfxpath=", NULL           },
        { "QT_INSTALL_ARCHDATA",     "qt_adatpath=", NULL           },
        { "QT_INSTALL_DOCS",         "qt_docspath=", "doc"          },
        { "QT_INSTALL_HEADERS",      "qt_hdrspath=", "include"      },
        { "QT_INSTALL_LIBS",         "qt_libspath=", "lib"          },
        { "QT_INSTALL_LIBEXECS",     "qt_lbexpath=", "libexec"      },
        { "QT_INSTALL_BINS",         "qt_binspath=", "bin"          },
        { "QT_INSTALL_PLUGINS",      "qt_plugpath=", "plugins"      },
        { "QT_INSTALL_IMPORTS",      "qt_impspath=", "imports"      },
        { "QT_INSTALL_QML",          "qt_qml2path=", "qml"          },
        { "QT_INSTALL_DATA",         "qt_datapath=", NULL           },
        { "QT_INSTALL_TRANSLATIONS", "qt_trnspath=", "translations" },
        { "QT_INSTALL_EXAMPLES",     "qt_xmplpath=", "examples"     },
        { "QT_INSTALL_DEMOS",        "qt_demopath=", "demos"        },
        { "QT_INSTALL_TESTS",        "qt_tstspath=", "tests"        },
        { "QT_HOST_PREFIX",          "qt_hpfxpath=", NULL           },
        { "QT_HOST_BINS",            "qt_hbinpath=", "bin"          },
        { "QT_HOST_DATA",            "qt_hdatpath=", NULL           }
    };

@carlos22

Suggestion for some vars:
qt_prfxpath=.

Does not work for me when the AppDir layout is in fhs-like style (i.e., lib/ is next to bin/). qt_prfxpath=.. does.

So, the question is, what does NULL translate to. We need, for example, qt_prfxpath=.. (because "On Windows and X11, the Prefix is relative to the directory containing the application executable (QCoreApplication::applicationDirPath()).") but possibly in all?/some? other instances . (because they may be relative to qt_prfxpath.)

@carlos22

qmake -query <VAR>

That will give you the values that the Qt from your system wants - not necessarily what we need for the layout that linuxdeployqt creates (unless we change the logic of linuxdeployqt to mirror the layout of the Qt that is being deployed, which I hope we won't need to because that would make the code much more complex, error-prone and less maintainable).

Owner

probonopd commented Mar 26, 2017

Check out QtBinPatcher source code from
http://repo.msys2.org/mingw/sources/mingw-w64-i686-qtbinpatcher-2.2.0-1.src.tar.gz
especially around here:

    static const TParam Params[] = {
        { "QT_INSTALL_PREFIX",       "qt_prfxpath=", NULL           },
        { "QT_INSTALL_ARCHDATA",     "qt_adatpath=", NULL           },
        { "QT_INSTALL_DOCS",         "qt_docspath=", "doc"          },
        { "QT_INSTALL_HEADERS",      "qt_hdrspath=", "include"      },
        { "QT_INSTALL_LIBS",         "qt_libspath=", "lib"          },
        { "QT_INSTALL_LIBEXECS",     "qt_lbexpath=", "libexec"      },
        { "QT_INSTALL_BINS",         "qt_binspath=", "bin"          },
        { "QT_INSTALL_PLUGINS",      "qt_plugpath=", "plugins"      },
        { "QT_INSTALL_IMPORTS",      "qt_impspath=", "imports"      },
        { "QT_INSTALL_QML",          "qt_qml2path=", "qml"          },
        { "QT_INSTALL_DATA",         "qt_datapath=", NULL           },
        { "QT_INSTALL_TRANSLATIONS", "qt_trnspath=", "translations" },
        { "QT_INSTALL_EXAMPLES",     "qt_xmplpath=", "examples"     },
        { "QT_INSTALL_DEMOS",        "qt_demopath=", "demos"        },
        { "QT_INSTALL_TESTS",        "qt_tstspath=", "tests"        },
        { "QT_HOST_PREFIX",          "qt_hpfxpath=", NULL           },
        { "QT_HOST_BINS",            "qt_hbinpath=", "bin"          },
        { "QT_HOST_DATA",            "qt_hdatpath=", NULL           }
    };

@carlos22

Suggestion for some vars:
qt_prfxpath=.

Does not work for me when the AppDir layout is in fhs-like style (i.e., lib/ is next to bin/). qt_prfxpath=.. does.

So, the question is, what does NULL translate to. We need, for example, qt_prfxpath=.. (because "On Windows and X11, the Prefix is relative to the directory containing the application executable (QCoreApplication::applicationDirPath()).") but possibly in all?/some? other instances . (because they may be relative to qt_prfxpath.)

@carlos22

qmake -query <VAR>

That will give you the values that the Qt from your system wants - not necessarily what we need for the layout that linuxdeployqt creates (unless we change the logic of linuxdeployqt to mirror the layout of the Qt that is being deployed, which I hope we won't need to because that would make the code much more complex, error-prone and less maintainable).

@probonopd

This comment has been minimized.

Show comment
Hide comment
@probonopd

probonopd Mar 26, 2017

Owner

So, my current working hypothesis is:

qt_prfxpath=.. # when in fhs-like mode (i.e., lib/ is next to bin/)
qt_prfxpath=. # when not in fhs-like mode (i.e., lib/ is next to the executable and there is no bin/)
qt_adatpath=.
qt_docspath=doc
qt_hdrspath=include
qt_libspath=lib
qt_lbexpath=libexec
qt_binspath=bin
qt_plugpath=plugins
qt_impspath=imports
qt_qml2path=qml
qt_datapath=.
qt_trnspath=translations
qt_xmplpath=examples
qt_demopath=demos
qt_tstspath=tests
qt_hpfxpath=.
qt_hbinpath=bin
qt_hdatpath=.
qt_stngpath=.

Plus patch away qt.conf loading from the system (e.g., /etc)

Owner

probonopd commented Mar 26, 2017

So, my current working hypothesis is:

qt_prfxpath=.. # when in fhs-like mode (i.e., lib/ is next to bin/)
qt_prfxpath=. # when not in fhs-like mode (i.e., lib/ is next to the executable and there is no bin/)
qt_adatpath=.
qt_docspath=doc
qt_hdrspath=include
qt_libspath=lib
qt_lbexpath=libexec
qt_binspath=bin
qt_plugpath=plugins
qt_impspath=imports
qt_qml2path=qml
qt_datapath=.
qt_trnspath=translations
qt_xmplpath=examples
qt_demopath=demos
qt_tstspath=tests
qt_hpfxpath=.
qt_hbinpath=bin
qt_hdatpath=.
qt_stngpath=.

Plus patch away qt.conf loading from the system (e.g., /etc)

@probonopd

This comment has been minimized.

Show comment
Hide comment
@probonopd

probonopd Mar 26, 2017

Owner

I am writing this logic now...

Owner

probonopd commented Mar 26, 2017

I am writing this logic now...

@probonopd

This comment has been minimized.

Show comment
Hide comment
@probonopd

probonopd Mar 26, 2017

Owner

@carlos22 @adrianschroeter please try the latest continuous build and report back how it goes. If it still doesn't work, then I suspect that it is loading some Trolltech.conf or qt.conf from your system; verify this by using strace and temporarily removing the offending conf file from your system (temporarily move it away). Or something like in #98 may be going on.

Owner

probonopd commented Mar 26, 2017

@carlos22 @adrianschroeter please try the latest continuous build and report back how it goes. If it still doesn't work, then I suspect that it is loading some Trolltech.conf or qt.conf from your system; verify this by using strace and temporarily removing the offending conf file from your system (temporarily move it away). Or something like in #98 may be going on.

@probonopd

This comment has been minimized.

Show comment
Hide comment
@probonopd

probonopd Mar 26, 2017

Owner

@carlos22 I think any remaining issues with distro Qt on Arch Linux may be unrelated to this, so let's continue on #98

Owner

probonopd commented Mar 26, 2017

@carlos22 I think any remaining issues with distro Qt on Arch Linux may be unrelated to this, so let's continue on #98

@carlos22

This comment has been minimized.

Show comment
Hide comment
@carlos22

carlos22 Mar 27, 2017

@probonopd yes thats what i expected. But good work with this issue 👍

carlos22 commented Mar 27, 2017

@probonopd yes thats what i expected. But good work with this issue 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment