Hi all!
I just tried to build TDE on FreeBSD 11.2 and found some problems:
1) The Makefile relies on "xorgproto", which does not exist on 11.2 (I think it can be found in 12). x11/xorgproto from ports conflicts with glproto etc., so it annot be used. Removing "xorgproto" from the Makefile works, of course.
2) tqt3 fails to build due to the system/compiler "freebsd-clang" is not present in ${QTBASE}/share/tqt3/mkspecs/freebsd-clang, but ${QTBASE}/share/tqt3/mkspecs/freebsd-g++ exists. Modifying the Makefile and replacing all "mkspecs/freebsd-clang" to "mkspecs/freebsd-g++" lets me build tqt3. Rebuild is in progress, so I don't know right now it this necessary for all Makefiles.
Nik
===> Configuring for tqt3-14.0.5
===> FreeBSD 10 autotools fix applied to /usr/home/nik/TDE/tde-packaging/freebsd/dependencies/tqt3/work/tqt-x11-free_14.0.5/src/3rdparty/libmng/aclocal.m4
===> FreeBSD 10 autotools fix applied to /usr/home/nik/TDE/tde-packaging/freebsd/dependencies/tqt3/work/tqt-x11-free_14.0.5/src/3rdparty/libmng/configure
The specified system/compiler is not supported:
/usr/home/nik/TDE/tde-packaging/freebsd/dependencies/tqt3/work/tqt-x11-free_14.0.5/mkspecs//usr/local/share/tqt3/mkspecs/freebsd-clang
Please see the PLATFORMS file for a complete list.
===> Script "configure" failed unexpectedly.
Please report the problem to slavek.banko(a)axis.cz [maintainer] and attach the
"/usr/home/nik/TDE/tde-packaging/freebsd/dependencies/tqt3/work/tqt-x11-free_14.0.5/config.log"
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. a /usr/local/sbin/pkg-static info -g -Ea).
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Hi all!
Ok, found another thing: tqt3 installes the file /usr/local/include/tqt3/ntqgplugin.h, which fails to compile tqtinterface. The origilal content of file /usr/local/include/tqt3/ntqgplugin.h, line 83, is:
static const char *qt_ucm_verification_data = \
"pattern=""QT_UCM_VERIFICATION_DATA""\n" \
"version="TQT_VERSION_STR"\n" \
"flags="Q_PLUGIN_FLAGS_STRING"\n" \
"buildkey="TQT_BUILD_KEY"\0";
This sould be:
static const char *qt_ucm_verification_data = \
"pattern=""QT_UCM_VERIFICATION_DATA""\n" \
"version=""TQT_VERSION_STR""\n" \
"flags=""Q_PLUGIN_FLAGS_STRING""\n" \
"buildkey=""TQT_BUILD_KEY""\0";
Then tqtinterface compiles.
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Hi to all devs,
I spent already some time looking at bluez5 and I started playing with dbus
recently. So I was wondering how to use dbusxml2qt3 more efficiently in
creating interfaces and how to use them in code. Proxies but they are
rather straight forward to use, so my attention was on publishing services.
I have seen on many places in the TDE source code a different approach
(directly using dbus), so I wrote a howto, for all of us that would like to
add kind of abstraction when working with dbus in the future.
As a result I can conclude that dbusxml2qt3 is worth some improvement (bug
fixing), but overall turned out to be very useful so far.
Most of all, as shown in the example, creating a nice service with it's
Introspectable interface can be achieved with very low effort.
https://wiki.trinitydesktop.org/TDE_DBus_Tutorial
I hope you like it
regards
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2018/08/06 05:35 AM, Dan Youngquist wrote:
> Maybe multi-megabyte screenshots could be emailed directly to Michele instead of posted to the list? One or two
> huge messages aren't much of a problem, but a bunch of them in a row can choke things up a bit for those of us
> without the fastest connections.
That sounds a good suggestion, perhaps send to me and Slavek together.
I should keep this in mind in future occasion :-)
And thanks to all those who have sent screenshots so far, some of them will look really good on a release page :-)
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAltnv0oACgkQKnW3yore
1c8+vA//ZFOmYeL/coQAv0m5afktUFgqSqC7PbT5RFV1VTlsOEUDp4Kw4Xj73x1A
dIUA7oq9H481mlwcBhetdTq5YlTlx5ptz0hplhqBSLyyWJQ+D1NpgbPMvv1dsBL6
PaxpLxepW95cOaltJ3/rdafe1z+XrngLEuVLOmAQNGIWZhGr8V0/noGaF8KrCGzW
kdjV7tZiPxp0Xvqt5Xs1F2asDmhUjThk1r8A5+E9Ep5C0YKVT1Ky55kOMnRdBmGF
tdUoQpv5Ko/HbQ8TAHnz5ceQPs0mnB+eg3UQl8N4uAIUC9WRgsagWX7fgFH3ZaSH
MBhOt+LONi1nYXM4T+n8oqJD0EQ73PrtdeHvFGV4AUoo3GejTyve7N4sGYao3kSk
PcC3U75Cg69wgy63Xr300LLT1N4EdmdH81KCcDkRTt1AoquaJaakQ2qPuFrKG9z6
Jy7YpgK+ylUbY/B0/f1hnb+DoMW4M5678bP0K0mqeXUF+KrAps6bE/cXNAU4TJcY
ugTvvusWQciuqzWejfGeEeCH9tSQ0kxYTzreFhcBFJ21NUWKkf/iGWSAt+T7QTNa
a0OUqbKsY2iJUNv4CnnIAQwlUvOjmssXMgzs5ktnn8yZXSXSg1nhGz/S1vz6UISg
duvuLWV307zCR5d7NBk4uisEKyTrZ7t9bwvXgXCFS2+XlzSZF2M=
=bfsi
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi everyone,
as you may know, we are getting ready for the release of R14.0.5 and we would like to update some of the screenshots
we have on the wiki and on the announcement link.
We think it is a good way to involve all of you in this: feel free to post your screenshots here on the ML for
consideration. Those selected, will make it to the Release page :-)
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAltnC78ACgkQKnW3yore
1c9QUw//Q50kz2CLC3fYmr/FKUD7ogkUWtDDM1NExWWPko2brh7CIOM0Fa4gqJPv
NtfSzQJLacsKFsjieLxDnruncBwzQOJIVSq8Re0+o8ciQw5X/KNtscP5Lso+sT8S
HLMYM8RjTOf6bGj7ni8LlkCfsDhBYtEGLuqlJbJpLv75PW+1yxa5Tb36d7Ag+wuy
x8LQ0VPEqxctMUQIhp+Dm5G2/tn6PMqcFGpVh94EkMBtSi3JdUjCew3qMr+c9rLT
wnwKKF0/STUyocNHIzUO+efKKOBlmqJn6DKsWz1kWM+L6jd0IP/yLiK3BKhLwyyP
tEJc+pwhJ+V4ILo/Rv0EILZTg70kTF6icWw9vIJPA+aBy5H85SJ6U4WS0Z6kZtKL
PZZAYHC+q9P59x4fkIRpkY82RxNO+CB11nAYrpDH5N17u11NcR6eGPpP7Y8blhAh
t5iZ6TdvTWf8SdNf2sE2zBg3jV3f9IkIkNbc8/NaHAjjqflzfjCtZ8dped0/Ddks
7HvCChl4XWuARP+QFKdDKreWqijqnAu6PdmRcsZGMrdSACyi0XAf636gcHVVF1+1
/V1oG6RDMrjytBqRQnyKhiZmxn2PtE6xBcVeCcy6/cRvl2ngYsNuqPYtU58hhb58
OX7NAJt+lbY4+lSrm/joyB9gGeimLQCWJNg48h1Ygz6/reH4qW4=
=PRc1
-----END PGP SIGNATURE-----
# dpkg -l | grep gtk
ii gtk3-tqt-engine-trinity 4:14.1.0~s12-0ubuntu18.04.0+3~a amd64 GTK3 theme engine for TDE
ii gtk-qt-engine-trinity 4:14.1.0~s14-0ubuntu18.04.0+3~a amd64 theme engine using Qt for GTK+ 2.x and Trinity
ii gtk-update-icon-cache 3.22.30-1ubuntu1 amd64 icon theme caching utility
ii kgtk-qt3-trinity 4:14.1.0~s14-0ubuntu18.04.0+1 amd64 Use TDE dialogs in Gtk apps
ii libcanberra-gtk3-0:amd64 0.30-5ubuntu1 amd64 GTK+ 3.0 helper for playing widget event sounds with libcanberra
ii libgtk2.0-0:amd64 2.24.32-1ubuntu1 amd64 GTK+ graphical user interface library
ii libgtk2.0-bin 2.24.32-1ubuntu1 amd64 programs for the GTK+ graphical user interface library
ii libgtk2.0-common 2.24.32-1ubuntu1 all common files for the GTK+ graphical user interface library
ii libgtk-3-0:amd64 3.22.30-1ubuntu1 amd64 GTK+ graphical user interface library
ii libgtk-3-common 3.22.30-1ubuntu1 all common files for the GTK+ graphical user interface library
ii libgtkmm-3.0-1v5:amd64 3.22.2-2 amd64 C++ wrappers for GTK+ (shared libraries)
# /usr/local/ffe60/firefox -P ffe60
(firefox:27799): Gtk-ERROR **: 04:42:18.938: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
ExceptionHandler::GenerateDump cloned child 27805
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Trace/breakpoint trap
(crashreporter:27810): Gtk-ERROR **: 04:42:19.016: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Anyone recognize whether this is a bug or missing or conflicting package? If missing
or conflict, which?
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Hi all,
by our joint effort we have gotten to the point where the list of issues
identified for R14.0.5 is empty. Please, do you have any more patches
that seems to be necessary before final freezing R14.0.5?
François, is everything ok to build on RPM distribution?
Cheers
--
Slávek
On Sun June 24 2018 10:14:39 Slávek Banko wrote:
> at mirror.xcer.cz, colleague has not yet made the removal of distributions
> that are no longer build for Preliminary Stable Builds. Therefore, packages
> for these distributions are still available on mirror.xcer.cz. While on
> mirror.ppa.trinitydesktop.org is cleaning old packages more actively. This
> is why the content may vary. Both of these mirrors are synchronized from my
> main server using apt-mirror. Therefore, removing old packages can be done
> differently on each mirror.
>
> If you want to synchronize Preliminary Stable Builds repository to your
> mirror, I can setup rsync on mirror.ppa.trinitydesktop.org. Would it be
> useful for you?
// Retitled and moved from trinity-users to trinity-devel.
Hi Slavek,
The mirrors are here to serve TDE so the question is what would be useful to
TDE devs and users?
Here's a little background FYI.
(1) The primary mirror has roughly 240GB of which 192GB is currently in use.
This can be increased but of course none of us want to spend more money
on renting data center disk space than necessary. I don't know how much
disk space is available for TDE on the secondary mirrors.
27G ./cdimages
1.7G ./git-images
14G ./libreoffice-trinity
38M ./openldap
24G ./releases
62G ./trinity
384M ./trinity-builddeps
1.5G ./trinity-builddeps-r14.0.0
929M ./trinity-builddeps-v3.5.13
1.5G ./trinity-nightly-build-dependencies
412K ./trinity-nightly-builds-01
41G ./trinity-r14.0.0
20G ./trinity-v3.5.13
553M ./ulab
(2) I have not yet exceeded monthly transfer limits and hope not to do so.
I can serve normal traffic and new releases but please contact mirror
admins before any overall reorganization which could be done more
efficiently with mv than rsync.
(3) I am not personally in direct contact with any of the other mirrors, even
though they all pull from us. Contact between the mirror admins has AFAIK
always been through Tim. We created the primary mirror to alleviate
bandwidth problems at Tim's build farm in the past when all mirrors
pulled direct from him.
(4) The primary mirror uses rsync rather than apt-mirror, and I suspect the
same is true for the other mirrors.
(5) I appreciate heads up on any planned major changes to mirror content so
I can increase monitoring and if necessary change mirroring parameters.
It might be best to provide such heads up off-list because ...
(6) To avoid overloading build farm bandwidth, it is best not to announce
releases until they are fully mirrored. If users start pulling unmirrored
files they are served from the build farm, overloading its bandwidth and
slowing mirroring, so things get very slow for everyone.
As a TDE user myself I would find it convenient but not critical if there
were fewer differences between PSB and Stable. Ideally they would be in
the same repo pool - like Debian testing and stable.
--Mike
(Same on both 42.3 and 15.0)
# zypper se -s qt | grep -i gtk
| qtcurve-gtk2 | package | 1.8.19~git20150303-4.2 | x86_64 | OSS
i+ | trinity-gtk-qt-engine| package | 2:0.8-14.0.4_1.oss423 | x86_64 | TDE
i+ | trinity-gtk3-tqt-engine| package | 2:0.5-14.0.4_1.oss423 | x86_64 | TDE
TCC > GTK Styles & Fonts > GTK2 Styles:
WARNING: The Gtk-Qt theme engine is not installed. This means you
will not be able to use your TDE style in GTK2 applications.
Exactly what package is this warning referring to?
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/