>> I've read through it until I'm blue in the face and I can't
>figure out what it
>> means to my build script. How are you building it? Obviously my
>build for
>> python-sip and python2-sip build but are now completely broken.
>I'm building with:
>>
>> CFLAGS="${CFLAGS} -I/usr/include/tqt -I${TDEDIR}/include -
>I${QTDIR}/include"
Grab a copy of my build scripts. There are some nominal changes in
the sip4-tqt and python-tqt scripts. Notice the changes in the
configuration section.
Rebuild both packages.
Darrell
Darrell, Slavek,
With a complete build (tqt3 -> tdeutils), tdeutils fails at 96% with the
following:
[ 96%] Building CXX object
superkaramba/src/CMakeFiles/superkaramba.dir/meter_python.cpp.o
cd /build/tde-tdeutils/src/build/superkaramba/src && /usr/bin/c++
-DHAVE_CONFIG_H -march=i686 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4 -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL
-DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include
tqt.h -I/opt/tqt3/include -I/usr/include/tqt -DQT_NO_ASCII_CAST
-DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION
-DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -I/build/tde-tdeutils/src/build
-I/build/tde-tdeutils/src/build/superkaramba/src
-I/build/tde-tdeutils/src/tdeutils/superkaramba/src -I/usr/include/python3.3m
-I/opt/trinity/include -I/opt/tqt3/include -I/usr/include/tqt -o
CMakeFiles/superkaramba.dir/meter_python.cpp.o -c
/build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp
In file included from
/build/tde-tdeutils/src/tdeutils/superkaramba/src/karamba.h:73:0,
from
/build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp:17:
/build/tde-tdeutils/src/tdeutils/superkaramba/src/imagelabel.h:41:14: warning:
declaration 'class TDEIO::CopyJob' does not declare anything [enabled by default]
class TDEIO::CopyJob;
^
/build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp: In function
'TQString PyString2TQString(PyObject*)':
/build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp:96:33: error:
'PyString_CheckExact' was not declared in this scope
if (PyString_CheckExact(text))
^
/build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp:98:41: error:
'PyString_AsString' was not declared in this scope
char* t = PyString_AsString(text);
^
/build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp: In function
'PyObject* TQString2PyString(TQString)':
/build/tde-tdeutils/src/tdeutils/superkaramba/src/meter_python.cpp:151:38:
error: 'PyString_FromString' was not declared in this scope
pyString = PyString_FromString("");
^
superkaramba/src/CMakeFiles/superkaramba.dir/build.make:973: recipe for target
'superkaramba/src/CMakeFiles/superkaramba.dir/meter_python.cpp.o' failed
make[2]: *** [superkaramba/src/CMakeFiles/superkaramba.dir/meter_python.cpp.o]
Error 1
make[2]: Leaving directory '/build/tde-tdeutils/src/build'
CMakeFiles/Makefile2:5060: recipe for target
'superkaramba/src/CMakeFiles/superkaramba.dir/all' failed
make[1]: *** [superkaramba/src/CMakeFiles/superkaramba.dir/all] Error 2
make[1]: Leaving directory '/build/tde-tdeutils/src/build'
Makefile:119: recipe for target 'all' failed
How to solve?
--
David C. Rankin, J.D.,P.E.
All,
As we continue to update the help handbooks, a significant
challenge is updating not only the text but the screen captures. I
would like to automate part of this process as much as possible.
The basic screen capture process:
* Save a new screen capture in English.
* Note the image size properties.
* Toggle to a different language.
* Verify the respective tde-i18n module is using that same image.
(Not all i18n modules support everything.)
* Save a new screen capture in the respective language with the
same image size properties.
* Repeat through all i18n languages.
I'm thinking we need a way to update all i18n po file references to
the original source file and code lines, as well as update the po
file English reference to what is now actually in the source code.
We've made many changes the past few years and the po file English
references are not current. Many code line references are incorrect.
We lack the project size needed to keep all of the i18n files
updated, but at least we can update the English references and
source code lines as well as the screen captures.
I am asking that you let this challenge fester for a while in your
subconcious and hopefully a solution emerges. These are not R14.0.0
priorities, but as Slavek mentioned previously, probably marked for
R14.0.2.
As always, thank you. :)
Darrell
>maybe tmplayer? I don't think the name matters all that much.
>there
>already exists smplayer, gnome-mplayer, kplayer and kmplayer
>according
>to my debian package list.
I meant a name change consistent with our previous name changes.
Not a priority.
Darrell
>I think that, in the end, we have three options:
>
>1. Get kaboodle up to snuff.
Yes, improving kaboodle to support all modern formats is a huge
bite. Short term we only need to debug and patch why kaboodle is
failing with even the older formats. That provides us some
temproary breathing room.
>2. Move kmplayer into tde-multimedia.
If we do this then we might consider pulling kaboodle from the
sources and abandon kaboodle.
I'm not against the idea of pulling kmplayer into tdemultimedia,
but another option is we promote kmplayer as part of the base
package set. If we start promoting kmplayer, I'm in favor of a name
change.
>3. Move kaffeine into tde-multimedia.
Same as kmplayer: we promote kaffeine as part of the standard
package set.
Darrell
>No, leave the patch in place - I'll make an update.
>I hope soon :)
Okay. I believe the path I used in the patch is the normal
installation location as intended from upstream. Therefore other
distro maintainers who use a different path are changing that
location.
Darrell
On Tuesday 04 February 2014 16:08:45 you wrote:
> >7) all distros support mplayer in one form or another
>
> I suppose this is a packager problem, but the original idea of a
> default player is no external dependencies.
>
> MPlayer is well supported but is not part of a stock installation
> on all distros. Other dependency presumptions exist in Trinity (for
> example, xine for amarok), yet nominating kmplayer as a default
> video player and moving into tdemultimedia means MPlayer needs to
> be installed.
>
> Audio players are not the same challenge. We have kaboodle, noatun,
> and juk, all installed by the base package tdemultimedia.
>
> Fixing kaboodle gets us half way home. The other half is update
> kaboodle to support newer generations of avi/mpg and like or not,
> probably should support flv. For a default player that will
> suffice. People who want extensive video format coverage are going
> to install something else anyway.
>
> For Trinity users those additional apps will be kaffiene and
> kmplayer for video and amarok for audio. Not a problem for those
> types of users. We are discussing a basic default video player for
> the first-time out-of-the-box Trinity experience.
>
> Darrell
Never could get kaboodle & kmplayer to 'just work' for random streaming
media, checking the 'depends' for those two comes up with a
signifcantly shorter list of codecs et al installed compared to mplayer
and (my fav) vlc. this is on a Debian system.
Problem with desktop environments, apps that no longer or never did
work, not being able to go outside the box and use best of breed apps.
TDE has some 'best' apps, mine=gwenview, digikam, k3b, kmail, can using
other non-tde apps be considered ? Is this what the gtk-qt widget stuff
is for?
--
Peace,
Greg
>I would like to tag the current sources and binaries R14.0.0 RC1,
>as it
>appears that we have finally cleared the Blocker and Critical
>reports from
>the R14 Etherpad.
>
>Are we ready for this or are there any objections?
The etherpad hasn't received updates in a while. We need some
hacking.
Blocker:
========
http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd
=Blocker
Critical:
=========
http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd
=Critical
Michele is working on 1825, but could use help. That is an ugly bug
from a public relations perspective. The comments provide a lot of
details.
1853 needs attention.
1821 hasn't been touched.
1813 can be closed after the last comment is implemented.
Regressions:
============
1825 is bad (already mentioned in Critical). The others should
receive attention but probably could survive the R14.0.0 cut.
Patches Available:
==================
Lots of patches sitting out there that have not been reviewed.
Likely many could be pushed.
Other:
======
* The new web site should be tested before moving toward a release
date.
* There is a laundry list of items in the R14 checklist etherpad
that need attention.
Darrell
>I've had success with 'xine' 'kmplayer' (very slow) 'mplayer' (ok
>but full screen) and 'kaffeine"
Yes, but those apps are not default apps. Kaboodle is the only base
app that plays videos.
Xine is indeed a dependency for several Trinity apps, but all of
those apps are not base installation apps, like amarok, kaffeine,
kmplayer, etc.
Darrell