tde-devels

devels@trinitydesktop.org

3 participants
3808 discussions

Application NOT respecting 'System Administration -> Paths' setting in kcontrol
by David C. Rankin 20 Apr '12

20 Apr '12

Tim, All, I don't like the default ~/Documents folder, so on my installs I always set 'System Administration -> Paths' (Document Paths:) to just /home/david. I've done that in tde, but then with every app I open (kate, kwrite, etc..) when I select 'open' it defaults to looking in the /home/david/Documents folder. It looks like tde is ignoring the setting. Anybody else see this in the latest GIT builds? -- David C. Rankin, J.D.,P.E.

2 3

python-tqt, python-trinity on 64-bit
by Darrell Anderson 20 Apr '12

20 Apr '12

I'm missing something obvious, but I can't get these packages to build on 64-bit. They can't find $PREFIX/lib64. I appreciate help. Darrell

2 10

Deb users - where do I find this patch? (wanted for kmplayer fix)
by David C. Rankin 20 Apr '12

20 Apr '12

Where can I find a link to this patch I need to look at to get an idea on a kmplayer patch: http://packages.debian.org/changelogs/pool/main/g/gopchop/current/changelog I need a link to: gopchop (1.1.8-5) unstable; urgency=low * Add patch to support build with gcc 4.7 (Closes: #667188) * Bump Standards-Version to 3.9.3 (no changes). -- tony mancill <tmancill(a)debian.org> Thu, 05 Apr 2012 04:44:31 +0000 I keep going in circles in the debian package pages. Before contacting the maintainer, I thought I would ask our debian users where to look for it... -- David C. Rankin, J.D.,P.E.

2 4

kmplayer - 'xine_gui_send_vo_data ' deprecated (GONE) from xine-lib - what to do?
by David C. Rankin 20 Apr '12

20 Apr '12

All, Looking at getting kmplayer built and I'm running into function that are so deprecated, they have been dropped from xine-lib/xine-ui - What to do here? Look at finding a compatible newer version of kmplayer that isn't that old that can replace the GIT source and build in todays world? How do these type issues get fixed? -- David C. Rankin, J.D.,P.E.

2 3

plan for dealing with fixing gcc47 '-fpermissive' requirement? What's usually involved?
by David C. Rankin 19 Apr '12

19 Apr '12

All, What is usually involved in updating the packages to get rid of the '-fpermissive' build flag requirement brought on by gcc47? What do you look for? Just remove '-fpermissive' and build over and over fixing along the way or is there a better way? By my count, the following packages require '-fpermissive' with gcc47: amarok digikam kaffeine kipi-plugins kmplayer (other issues as well) koffice (still requires libpng15 fixes) krusader python-tqt rosegarden tdeadmin tdebase tdeedu tdegames tdegraphics tdepim Those are just those out of the packages I have built. There are probably others as well. Any suggestions? -- David C. Rankin, J.D.,P.E.

2 1

tqca, tqca-tls on 64-bit
by Darrell Anderson 19 Apr '12

19 Apr '12

Has anyone been building tqca and tqca-tls as 64-bit packages? They fail for not finding libtqt-mt.so. This is the snippet from the configure file: ============================================ if [ "$?" != "0" ]; then rm -rf .qconftemp echo fail echo echo "There was an error compiling 'conf'. Be sure you have a proper" echo "TQt 3.x Multithreaded (MT) build environment set up." if [ ! -f "$QTDIR/lib/libtqt-mt.so.3" ]; then echo echo "One possible reason is that you don't have" echo "libtqt-mt.so.3 installed in $QTDIR/lib/." fi echo exit 1; fi ============================================ I have $LIBDIR exported as /opt/trinity/lib64, but the tqca/tqca-tls configuration seems to be hard-coded to $PREFIX/lib. I'm probably missing something obvious because I see oodles of 64-bit RPM packages online, meaning the packages build on 64-bit. Currently I have all Trinity related 64-bit lib files installing to /opt/trinity/lib64. I'm just beginning to build everything for 64-bit, but other than these two packages, I seem to be proceeding okay. I'm presuming the two need to be patched or I have something misconfigured in my build scripts. Thanks. Darrell

1 0

SOLVED: digikam libpng15 + gcc47 - But: 'color_type' -- Is This Correct??
by David C. Rankin 19 Apr '12

19 Apr '12

All, I have built digikam on libpng15. There were two simple fixes for: if (setjmp(png_jmpbuf(png_ptr))) The remaining errors involved: digikamthumbnail.cpp:416:17: error: invalid use of incomplete type 'png_info {aka struct png_info_def}' In file included from digikamthumbnail.cpp:96:0: /usr/include/png.h:726:16: error: forward declaration of 'png_info {aka struct png_info_def}' digikamthumbnail.cpp:419:17: error: invalid use of incomplete type 'png_info {aka struct png_info_def}' In file included from digikamthumbnail.cpp:96:0: /usr/include/png.h:726:16: error: forward declaration of 'png_info {aka struct png_info_def}' digikamthumbnail.cpp:425:17: error: invalid use of incomplete type 'png_info {aka struct png_info_def}' In file included from digikamthumbnail.cpp:96:0: The above all involved references like: if (info_ptr->color_type == PNG_COLOR_TYPE_RGB_ALPHA) I know the 'info_ptr->color_type' is the problem. That's wrong due to no longer having direct access to the png struct. Looking at other patches, it looked like I could simply do: if (color_type == PNG_COLOR_TYPE_RGB_ALPHA) Since we have already made the call to: png_get_IHDR(png_ptr, info_ptr, (png_uint_32 *) (&w32), (png_uint_32 *) (&h32), &bit_depth, &color_type, &interlace_type, NULL, NULL); color_type should already hold the color type. So is just using 'color_type' correct? Digikam builds fine, but I need somebody to verify the patch. Darrell, we will need to add preprocessor checks for the libpng version. I haven't done that yet. The consolidated patch is attached for review. -- David C. Rankin, J.D.,P.E.

3 13

Building for 64-bit
by Darrell Anderson 19 Apr '12

19 Apr '12

I'm updating my build scripts to support 64-bit packages. Should (T)Qt3 install the lib files to $PREFIX/lib or $PREFIX/lib64? Thanks. Darrell

2 3

Building against Qt3 Fails
by Darrell Anderson 19 Apr '12

19 Apr '12

I decided to build against Qt3 rather than TQt3. First time in a long time. The patch we used recently to build avahi-tqt against TQt3 can't be used when building against Qt3. The patch is good only when building against TQt3. I presume the proper way to implement the patch is to add some preprocessor checks so packagers don't have to worry about the issue. For myself I added the following test in my avahi-tqt build script: if [ -r ${PREFIX}/lib/pkgconfig/tqt-mt.pc ] || [ -r /usr/lib/pkgconfig/tqt-mt.pc ]; then cat $CWD/avahi-tqt-fixes.diff | patch -p1 --verbose --no-backup-if-mismatch || exit 1 fi tdebase fails to build: /dev/shm/tdebase.build/kicker/kicker/core/kmenubase.ui.h:7: error: 't_xdisplay' was not declared in this scope As neither tqt_xdisplay nor qt_xdisplay is used in the source file, why does the file compile against TQt3 and not Qt3? Darrell

1 2

tqqt_cast vs. tqt_cast
by Darrell Anderson 19 Apr '12

19 Apr '12

What is the differnce? Darrell

2 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels