Re: Qt install binary path
On jueves, 29 de septiembre de 2016 4:45:10 P. M. ART Dmitry Shachnev wrote: [snip] > For the record: it was succeeding for builds where Build-Depends-Indep were > installed, because qttools5-dev-tools pulls in libqt5quick5 (via webkit). Ah, that explains it quite well. Thanks *a lot* Dmitry for digging into this! -- The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. George Bernard Shaw Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part. -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: Qt install binary path
Hi all, On Wed, Sep 28, 2016 at 08:11:31PM +0200, Sandro Knauß wrote: > > Well, yesterday I took your branch and build it without issues (tests ran > > just fine). But somehow buildds seems to disagree with me, as it seems a > > test is failing there. > > > > Is there anything I might be missing? > > I don't know. From the tests it is the qmlplugindumper, this actually should > list all plugins. So it maybe a problem for him to find the correct path for > the plugins? Maybe some envrionment variable got from our systems ( with a > KDE5 running) into sbuild and makes the test passing? Or any writepermission > on the buildds stops one try to write a file? I have added some qDebug() calls, and the build on Launchpad tells me this: /«PKGBUILDDIR»/bin/qmlplugindump: error while loading shared libraries: libQt5Quick.so.5: cannot open shared object file: No such file or directory Setting LD_LIBRARY_PATH=$(CURDIR)/lib should fix this issue, I will test and upload that now. While I am here, a note regarding your changes. Please never use dbus-launch and/or dbus-x11 package. See [1] for details. I have now reverted that in Git. [1]: https://lists.debian.org/debian-devel/2016/08/msg00554.html -- Dmitry Shachnev signature.asc Description: PGP signature -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: Qt install binary path
Hey, Thanks a lot for uploading! > Well, yesterday I took your branch and build it without issues (tests ran > just fine). But somehow buildds seems to disagree with me, as it seems a > test is failing there. > > Is there anything I might be missing? I don't know. From the tests it is the qmlplugindumper, this actually should list all plugins. So it maybe a problem for him to find the correct path for the plugins? Maybe some envrionment variable got from our systems ( with a KDE5 running) into sbuild and makes the test passing? Or any writepermission on the buildds stops one try to write a file? The passing powerpcspe build looks like that it fails to start xvfb or dbus, so it goes on with installation right away. Regards, sandro signature.asc Description: This is a digitally signed message part. -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: Qt install binary path
On miércoles, 28 de septiembre de 2016 12:10:10 A. M. ART Sandro Knauß wrote: > Hey, > > thanks for your great tipps. Finally I got the tests running with xvfb and > the patched locations: > > https://anonscm.debian.org/cgit/users/hefee-guest/qtdeclarative.git/commit/? > id=281e19175a701a1906377373eda92d9914e82094 > > Still I need to disable some tests, but I'm too tired for now to test again > if the list is the minimal one... Well, yesterday I took your branch and build it without issues (tests ran just fine). But somehow buildds seems to disagree with me, as it seems a test is failing there. Is there anything I might be missing? -- ...man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons. Douglas Adams, "The hitchhikers' guide to the galaxy" Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part. -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Qt install binary path
Hey,
I try currently to enable tests for qtdeclarative. So far it all works fine,
but the tests using:
QLibraryInfo::location(QLibraryInfo::BinariesPath) + QLatin1String("/
qmlscene")
to run qmlscene. The problem with that is that qmlscene is also part of the
package and is not installed obviously.
The binary is already build in $(CURDIR)/bin.
But the Qt Documentation tells that QLibraryInfo always returns a hardcoded
path, that can't be changed.
Is there a way to treat the tests to use the new builded qmlscene?
Or should I change the tests to not use QLibraryInfo?
See my repo about the way I run the tests:
https://anonscm.debian.org/cgit/users/hefee-guest/qtdeclarative.git/tree/
debian/rules
(sidenote: As a workaround I install qmlscene and qtdeclarative5-dev-tools to
pass the tests,
just if you are wondering about the debian/control in my repo).
Best Regards,
sandro
signature.asc
Description: This is a digitally signed message part.
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
