[Python-modules-team] Bug#751531: libqt5scintilla2-dev: qmake features file seems to be installed in the wrong location
Hi! It looks like that affects also the header files. Using the installed Qt/qmake, they are searched in /usr/include/x86_64-linux-gnu/qt5 but the dev package installs the Qsci headers in /usr/include/qt5. Using QMAKEFEATURES=/usr/share/qt5/mkspecs/features qmake picks up the prf file, but compilation failes when using includes like Qsci/qscilexercpp.h Is it ok to leave the 3 topics in a single bug report? * location of the prf file * location of the header files * wrong library name for Qt5 if debug is enabled I don't know if other file types like the translation files are also searched in different folders as we currently don't have translation enabled in the application (OpenSCAD). -- Torsten. ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#751531: libqt5scintilla2-dev: qmake features file seems to be installed in the wrong location
Yes. It's fine to keep them all in one bug. Translations aren't architecture specific so I'd guess the current location for the Qt5 translation is fine ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#751531: libqt5scintilla2-dev: qmake features file seems to be installed in the wrong location
On Tuesday, June 17, 2014 19:02:32 Torsten Paul wrote: Hi! It looks like that affects also the header files. Using the installed Qt/qmake, they are searched in /usr/include/x86_64-linux-gnu/qt5 but the dev package installs the Qsci headers in /usr/include/qt5. Using QMAKEFEATURES=/usr/share/qt5/mkspecs/features qmake picks up the prf file, but compilation failes when using includes like Qsci/qscilexercpp.h Is it ok to leave the 3 topics in a single bug report? * location of the prf file * location of the header files * wrong library name for Qt5 if debug is enabled In 2_2.8.2+dfsg-2 that arrived in Testing today the header file location should already be fixed. Please check. Scott K ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#751531: libqt5scintilla2-dev: qmake features file seems to be installed in the wrong location
Package: libqt5scintilla2-dev Version: 2.8.1-4 Severity: important The features file is installed in /usr/share/qt5/mkspecs/features/qscintilla2.prf but qmake seems to only read from /usr/lib/x86_64-linux-gnu/qt5/mkspecs/features. This causes qmake not to see the file with just qmake CONFIG+=qscintilla2 In addition the rename of -lqscintilla2 to -lqt5scintilla2 for Qt5 is only active in case debug is not defined. In case the project uses CONFIG+=debug, the wrong library name is used. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.0dali-1+ (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libqt5scintilla2-dev depends on: ii libqt5scintilla2-11 2.8.1-4+b1 ii qtbase5-dev 5.2.1+dfsg-3 libqt5scintilla2-dev recommends no packages. libqt5scintilla2-dev suggests no packages. -- no debconf information ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#751531: libqt5scintilla2-dev: qmake features file seems to be installed in the wrong location
On Friday, June 13, 2014 21:47:55 Torsten Paul wrote: Package: libqt5scintilla2-dev Version: 2.8.1-4 Severity: important The features file is installed in /usr/share/qt5/mkspecs/features/qscintilla2.prf but qmake seems to only read from /usr/lib/x86_64-linux-gnu/qt5/mkspecs/features. This causes qmake not to see the file with just qmake CONFIG+=qscintilla2 In addition the rename of -lqscintilla2 to -lqt5scintilla2 for Qt5 is only active in case debug is not defined. In case the project uses CONFIG+=debug, the wrong library name is used. Thanks for the feedback. I'm not actually using it for Qt5 and the .prf file is new in 2.8.1 and later in any case, so it's great to have someone who is that can test it. The install location is where the upstream build system puts it, but that doesn't make it right. There is currently an upload in unstable that needs to get to jessie/testing before I upload again to fix this, but I ought to be able to fix it next week. Scott K signature.asc Description: This is a digitally signed message part. ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
