Hi,
In Debian/Ubuntu, we received some bug reports ([1], [2], [3]) stating
that compiling QtWebKit apps fails with ld errors like this one:
/usr/bin/ld: cannot find -lgstapp-0.10
/usr/bin/ld: cannot find -lgstinterfaces-0.10
...
After digging the problem, we found out that the
against
that.
Kind regards,
--
Dmitry Shachnev (on behalf on Debian Qt maintainers)
signature.asc
Description: OpenPGP digital signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
code is still missing.
The full build log is here (for Qt 5.2.1):
https://launchpadlibrarian.net/168953728/buildlog_ubuntu-trusty-arm64.qtbase-opensource-src_5.2.1%2Bdfsg-1ubuntu7_UPLOADING.txt.gz
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
not help.
Does anybody know what may cause this behavior?
Kind regards,
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo
. Actually, when it works, it works without the port
number.
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Qt no longer reads theme settings from configuration files.
Is that correct? If yes, maybe it makes sense to drop qtconfig completely
from the repository?
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
___
Development mailing
On Tue, 23 Dec 2014 16:06:51 -0200, Thiago Macieira wrote:
On Tuesday 23 December 2014 16:52:51 Dmitry Shachnev wrote:
Hi all,
Back in 2011, there was a qttools commit (a22e38aee14419428bd5) that
commented out building of qtconfig on unix systems “to make tools compile”.
Almost 4 years
. Fedora ships it.
So my question is: can we drop the QGtkStyle completely and port the gtk
platform theme to GTK+ 3? I will contribute to that effort if it gets the
consensus.
[1]: https://bugs.debian.org/781148
[2]: https://github.com/MartinBriza/adwaita-qt
--
Dmitry Shachnev
signature.asc
need to
keep gtk2 theme if we have gtk3 theme?
Also the latter patch will need some rebasing for new version and new
copyrights.
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
___
Development mailing list
Development@qt
Hi,
On Mon, 26 Oct 2015 12:43:48 +0100, Marc Mutz wrote:
> It failed all of yesterday. Now works. Cf. e.g.
> https://codereview.qt-project.org/138771
Exactly, it works now for me too.
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital sig
/build_02131/macx-clang_developer-build_OSX_10.9/log.txt.gz
Can someone please look at that?
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman
ity of QLockFile in qtcore (introduced in Qt 5.1).
The QtSingleApplication will probably need to be ported to QLockFile instead.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
? If yes, is there any known workaround?
The build logs are available at:
https://buildd.debian.org/status/package.php?p=qtwebkit-opensource-src=experimental
--
Dmitry Shachnev
signature.asc
Description: PGP signature
___
Development mailing
sent in the command line.
>
> This patch should help:
>
> https://codereview.qt-project.org/#/c/150601
Thanks a lot! How could I not notice it…
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
___
Development mailing list
Develo
low
> all dependencies to be built" seems hard to achieve.
The GTK+ platform theme is actually a plugin (the libqgtk2.so file). Maybe
it can be built and/or distributed separately?
The biggest issue with missing GTK+ theme one needs to be aware of is that
Qt won't be able to detect the s
h back to the obsolete
> gzip.
+1, please leave tar.xz instead of tar.gz.
Users of all modern UNIX-like systems are able to decompress tar.xz, so .gz
has really no advantage over .xz.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
___
/
--
Dmitry Shachnev
signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
ers,
--
Dmitry Shachnev
signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
g code in qtbase, rather than relying
on a 3rdparty library:
https://code.qt.io/cgit/qt/qtbase.git/tree/src/platformsupport/themes/genericunix/dbustray/qxdgnotificationproxy_p.h
--
Dmitry Shachnev
signature.asc
Description: PGP signature
___
Development ma
ther than
> Qt_5_PRIVATE_API?
I think Qt_5_PRIVATE_API is enough. (But I won't mind if something different
is used, provided that it does not change from release to release.)
--
Dmitry Shachnev
signature.asc
Description: PGP signature
___
Development
://wiki.debian.org/ArchitectureSpecificsMemo#Summary for the full
list of Debian architectures with their endianness.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
elp us (Debian) a lot if Qt had something big endian on the CI.
Currently big endian support breaks with almost every major Qt release.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-projec
22 matches
Mail list logo
