tde-devels

devels@trinitydesktop.org

9 participants
3775 discussions

[PATCH] Make tqtinterface use Qt default lib path by default

by /dev/ammo42

Hello, The upstream tqtinterface uses by default a qt library path of $QTDIR/lib$LIBDIRSUFFIX, but Qt uses lib instead of lib64 within its "private" directory: -with the default build options, both for qt3 and qt4 -in the Debian Squeeze qt3 package. The patch attached to this e-mail solves this inconsistency and makes TQt3 build successfully with default options on Slackware, without specifying the Qt libdir.

13 years, 11 months

Qt3 support will be removed from Qt 4.8

by Ilya Chernykh

Just for your awareness.

13 years, 11 months

qt3 3.3.8c work folk with analisis and patches

by PICCORO McKAY Lenz

i finish the qt3 work by my own, if interesting, can view the complete work on http://www.shutendouji.net/massenkoh/projects/qt3/ this are tested on debian etch, lenny, squeeze, and geento & funtoo, on x86, and some amd64 atom laptops, also tested on hurd (over virtual machine) theres a compiled qt 3.3.8c-1 package folow stric debian policy also. the debian source list entry its " deb http://www.shutendouji.net/massenkoh/projects/qt3/ ./ " for the pqt3 3.3.8c package entry only, with support for build under amd_64, x86 and hurd, geento ebuild its on work progress on msktoo.blogspot.com i will post a blog and info entry in few days explain with better english all work in deep! On Tue, May 24, 2011 at 7:43 PM, /dev/ammo42 <mickeytintincolle(a)yahoo.fr>wrote: > Hello, > Here is (attached to this e-mail) the patch that enabled me to build > the Qt3 SVN tree with only Slackware-specific patches and the libpng14 > patch as supplementary patch, on my Slackware64 13.37 with Qt4 and KDE4 > installed alongside, and with /opt/kde3 prefix. > The patch: > —adds include/ symlinks which were present in qt-3.3.8b but not in SVN. > Especially, there was no symlink in include/private. > —but removes the include/png.h symlink, since nobody in their right > mind would use the included libpng 1.2.5, and the build system puts the > internal -I before -I/usr/include, making the build fail on > libpng-1.4-only systems because it uses the libpng-1.2.5 include instead > of the 1.4.5 one. Let's just let the user specify the libpng include if > it is nonstandard (BTW, I have some doubts regarding qt3's abilities to > detect libpng, since it didn't -I/usr/include/libpng14, the latter > being the include path specified in my libpng.pc). > —adds a missing #include <cstdlib> in qdesktopwidget_x11.c. > Did someone build the SVN version of Qt3 on distributions other than > Debian/Ubuntu or Slackware ? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > trinity-devel-unsubscribe(a)lists.pearsoncomputing.net > For additional commands, e-mail: > trinity-devel-help(a)lists.pearsoncomputing.net > Read list messsages on the Web archive: > http://trinity-devel.pearsoncomputing.net/ > Please remember not to top-post: > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting > -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.

13 years, 11 months

[PATCH] Qt3 SVN now builds on Slackware64 13.37

by /dev/ammo42

Hello, Here is (attached to this e-mail) the patch that enabled me to build the Qt3 SVN tree with only Slackware-specific patches and the libpng14 patch as supplementary patch, on my Slackware64 13.37 with Qt4 and KDE4 installed alongside, and with /opt/kde3 prefix. The patch: —adds include/ symlinks which were present in qt-3.3.8b but not in SVN. Especially, there was no symlink in include/private. —but removes the include/png.h symlink, since nobody in their right mind would use the included libpng 1.2.5, and the build system puts the internal -I before -I/usr/include, making the build fail on libpng-1.4-only systems because it uses the libpng-1.2.5 include instead of the 1.4.5 one. Let's just let the user specify the libpng include if it is nonstandard (BTW, I have some doubts regarding qt3's abilities to detect libpng, since it didn't -I/usr/include/libpng14, the latter being the include path specified in my libpng.pc). —adds a missing #include <cstdlib> in qdesktopwidget_x11.c. Did someone build the SVN version of Qt3 on distributions other than Debian/Ubuntu or Slackware ?

13 years, 11 months

Re: [trinity-devel] Hosting a Mirror

by Roman

Hi, On Monday 23 May 2011 12:15:11 Robert Xu wrote: > On May 22, 2011, at 23:01, Calvin Morrison <mutantturkey(a)gmail.com> wrote: > > Tim, All, > > > > I recently got my hands on a VPS that I don't have much use for. > > > > It has 300Gb / Month bandwidth, and I certainly won't be using it that > > extensively. > > > > Would it be suitable as an mirror? > > Mirrors take up a hell of a lot of bandwidth... maybe someone could provide some statistics on that... if it is not too much i might also be able to help out.. greetings, Roman -- -- Don't hit me!! I'm in the Twilight Zone!!!

13 years, 11 months

Hosting a Mirror

by Calvin Morrison

Tim, All, I recently got my hands on a VPS that I don't have much use for. It has 300Gb / Month bandwidth, and I certainly won't be using it that extensively. Would it be suitable as an mirror? Calvin Morrison

13 years, 11 months

Where Have the Styles Gone?? (No Keramic, No Plastic, etc..) Missing in current builds.

by David C. Rankin

Guys, In the latest builds, the widget styles are gone. Plastic (old default) and Keramic styles are nowhere to be found. Here is a screenshot of what is available: [54k] http://www.rlfpllc.com/dl/tde/ss/no-styles-800.jpg Do we have new build options that we have to give to enable them? I didn't do anything different in building that would effect what styles got built - what gives? -- David C. Rankin, J.D.,P.E.

13 years, 11 months

KLaptopDaemon

by Tiago Marques

Hi all, I've been using kpowersave for some time now but just noticed an old package by the name of klaptopdaemon. It seems to need some updating but, as someone who as not yet fully jumped into Trinity, I'd like to ask if it has been dropped or patched. While kpowersave works mostly ok, the integration of suspend/resume and hibernate with the system menu is not without flaws. How does Trinity handle these situations in laptops and what can it be done to improve it? Best regards, Tiago

13 years, 11 months

kdegraphics gcc46 - patch

by David C. Rankin

Tim, Could you add the following (attached) patch to kdegraphics/kviewshell/plugins/djvu/libdjvu/GSmartPointer.h -- David C. Rankin, J.D.,P.E.

13 years, 11 months

Qt3 code analysis, qt-x11-3.3.8b source compared to trinitydesktop (svn)

by David C. Rankin

Guys, After working to build Qt3 from svn for a day, it became clear that a bit of cleanup will be needed on the code before and getting a handle on what patches it contains before it can be usable. I took a bit of time tonight to analyze the qt-x11-3.3.8b source compared to the trinitydesktop (svn) code in hope of helping move this process along. The script I used is here: http://www.3111skyline.com/dl/dt/trinity/arch/scr/qt3srccmp.sh The basic setup for running the script is contained in a comment in the top of the script: #!/bin/bash --norc ## this presumes you have: ## ## (1) downloaded the trinity desktop qt3 source with svn checkout ## (2) removed the .svn files (tar --exclude-vcs -czf qt3svn.tar.gz qt3/), then untarred the files in a 'tmp-dir/qt3' ## (3) untarred the qt3-3.3.8b source into the same 'tmp-dir/qt-x11-free-3.3.8b' # The script then loops through the files in qt-x11-3.3.8b/ and compares the files to those in trinitydesktop qt3 (svn). The script summary provides: 6420 - files examined files in both Qt3 (svn) and qt-x11-free-3.3.8b, reported in: identical-svn-338b.txt files in qt-x11-free-3.3.8b but not in Qt3 svn, reported in: missing-svn-338b.txt diffs for files present in both with differing contents in : qtdiffs/path/to/filename.diff All results are available in the tarball available here: [99k] http://www.3111skyline.com/dl/dt/trinity/arch/dev/qt3-compare/qt3-svn-v-3.3… Files included: -> identical-svn-338b.txt - The script identifies those files that are identical between 3.3.8b code and svn (not that interesting, but useful for knowing which patches must still be applied; -> missing-svn-338b.txt - The files that are included in qt-x11-free-3.3.8b but are MISSING in trinitydesktop qt3 (svn). This is interesting: examples/opengl/overlay_x11/utilities/sovinfo/Makefile examples/opengl/overlay_x11/utilities/glxvisuals/Makefile extensions/nsplugin/examples/Makefile doc/Makefile src/3rdparty/Makefile src/3rdparty/zlib/Makefile The most important output is the identification of those file present in both source trees, but where the content of the files differs. This is wher many of the problem lie, and where work will need to be done to identify what patches have been previously applied and those that still need to be applied (or those that can be removed). This information is contained in 'diff' files created for each file where this difference was encountered. The diff files are contained under the qtdiff directory in the tarball (in proper hierarchy and effect the following files: qmake/option.cpp.diff mkspecs/hurd-g++/qmake.conf.diff mkspecs/linux-g++/qplatformdefs.h.diff mkspecs/linux-g++/qmake.conf.diff mkspecs/linux-g++-64/qmake.conf.diff examples/demo/opengl/fbm.h.diff examples/demo/opengl/fbm.c.diff tools/makeqpf/makeqpf.pro.diff tools/makeqpf/main.cpp.diff tools/mergetr/mergetr.pro.diff tools/msg2qm/msg2qm.pro.diff tools/tools.pro.diff tools/designer/designer.pro.diff tools/designer/tools/createcw/createcw.pro.diff tools/designer/uic/form.cpp.diff tools/designer/integration/designer.el.diff tools/qvfb/qvfbview.cpp.diff tools/qvfb/pda.skin.diff tools/qvfb/qvfb.cpp.diff tools/qtconfig/mainwindow.cpp.diff tools/qtconfig/mainwindow.h.diff tools/qtconfig/mainwindowbase.ui.diff tools/qembed/qembed.pro.diff doc/html/qglobal-h.html.diff src/codecs/qutfcodec.cpp.diff src/widgets/qpopupmenu.h.diff src/widgets/qcombobox.cpp.diff src/widgets/qtextedit.cpp.diff src/widgets/qtextedit.h.diff src/widgets/qscrollview.cpp.diff src/widgets/qtooltip.cpp.diff src/widgets/qmenubar.cpp.diff src/widgets/qbutton.h.diff src/widgets/qpopupmenu.cpp.diff src/widgets/qlineedit.h.diff src/widgets/qlistview.cpp.diff src/widgets/qlineedit.cpp.diff src/kernel/qdragobject.h.diff src/kernel/qfontengine_x11.cpp.diff src/kernel/qrichtext.cpp.diff src/kernel/qapplication_x11.cpp.diff src/kernel/qclipboard_x11.cpp.diff src/kernel/qfontdatabase_x11.cpp.diff src/kernel/qinputcontext_x11.cpp.diff src/kernel/qwidget.h.diff src/kernel/qrichtext_p.h.diff src/kernel/qt_kernel.pri.diff src/kernel/qwidget_x11.cpp.diff src/kernel/qobject.h.diff src/kernel/qapplication.cpp.diff src/kernel/qdnd_x11.cpp.diff src/kernel/qobject.cpp.diff src/kernel/qapplication.h.diff src/kernel/qpixmap_x11.cpp.diff src/kernel/qwidget.cpp.diff src/kernel/qdesktopwidget_x11.cpp.diff src/kernel/qt_x11_p.h.diff src/kernel/qnamespace.h.diff src/kernel/qdragobject.cpp.diff src/kernel/qevent.cpp.diff src/kernel/qfontdatabase.cpp.diff src/tools/qstring.h.diff src/tools/qlibrary.cpp.diff src/tools/qlocale.cpp.diff src/tools/qdir_unix.cpp.diff src/tools/qglobal.h.diff src/tools/qfeatures.h.diff src/tools/qfileinfo_unix.cpp.diff src/qt.pro.diff src/sql/drivers/odbc/qsql_odbc.h.diff src/sql/drivers/ibase/qsql_ibase.cpp.diff src/sql/qt_sql.pri.diff src/dialogs/qdialog.cpp.diff src/iconview/qiconview.cpp.diff src/opengl/qgl_x11.cpp.diff plugins/src/sqldrivers/odbc/odbc.pro.diff plugins/src/sqldrivers/ibase/ibase.pro.diff plugins/src/src.pro.diff configure.diff The file diff-file-list.txt in the tarball contains this index. I suspect the diffs above are the reason I can build from the 3.3.8b code, but my build from svn crashes. That's it for tonight. This will allow us to get a handle on what we have in the qt3 svn dir. Depending on how well documented all the current patches are that have been applied to the qt3 code in svn, it may be quicker to save the current qt3 dir on the server and to just start over with the qt-x11-3.3.8b code. It still builds fine with minimum patching. (you guys make that call) Feel free to add/remove whatever you like from the qt3srccmp.sh script. It is as flexible as you want to make it. Adding a bash statement or 2 will allow you to get 99.9% of the information you want from the two source trees. Hope this helps :) -- David C. Rankin, J.D.,P.E.

13 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels