tde-devels

devels@trinitydesktop.org

9 participants
3775 discussions

by Darrell Anderson

Today I am building packages using TQt3 rather than Qt3. Overall, a good day but I encountered some errors I did not experience with Qt3. ====================================================== tdegraphics: [ 10%] Building CXX object kghostview/CMakeFiles/kghostviewlib-shared.dir/kgvshell.cpp.o cd /dev/shm/tdegraphics.build/kghostview && /usr/bin/c++ -Dkghostviewlib_shared_EXPORTS -DHAVE_CONFIG_H -O2 -march=i486 -mtune=i686 -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -fPIC -I/dev/shm/tdegraphics.build/kghostview -I/dev/shm/tdegraphics/kghostview/dscparse -I/dev/shm/tdegraphics.build -I/opt/trinity/include -I/usr/include/tqt -o CMakeFiles/kghostviewlib-shared.dir/kgvshell.cpp.o -c /dev/shm/tdegraphics/kghostview/kgvshell.cpp /dev/shm/tdegraphics/kiconedit/utils.cpp: In function 'void setupImageHandlers()': /dev/shm/tdegraphics/kiconedit/utils.cpp:40: error: 'Q_CHECK_PTR' was not declared in this scope make[2]: *** [kiconedit/CMakeFiles/kiconedit.dir/utils.cpp.o] Error 1 make[2]: Leaving directory `/dev/shm/tdegraphics.build' ... In file included from /dev/shm/tdegraphics/kghostview/kgvshell.cpp:35: /opt/trinity/include/kedittoolbar.h:271: warning: 'KEditToolbarWidget' has a field 'KEditToolbarWidget::m_inactiveList' whose type uses the anonymous namespace /opt/trinity/include/kedittoolbar.h:271: warning: 'KEditToolbarWidget' has a field 'KEditToolbarWidget::m_activeList' whose type uses the anonymous namespace /dev/shm/tdegraphics/kghostview/kgvdocument.cpp: In member function 'void KGVDocument::doOpenFile()': /dev/shm/tdegraphics/kghostview/kgvdocument.cpp:131: error: 'Q_CHECK_PTR' was not declared in this scope /dev/shm/tdegraphics/kghostview/kgvdocument.cpp: In member function 'bool KGVDocument::uncompressFile()': /dev/shm/tdegraphics/kghostview/kgvdocument.cpp:199: error: 'Q_CHECK_PTR' was not declared in this scope make[2]: *** [kghostview/CMakeFiles/kghostviewlib-shared.dir/kgvdocument.cpp.o] Error 1 ====================================================== Darrell

13 years, 2 months

TQt3/tdebinding build errors

by Darrell Anderson

Today I am building packages using TQt3 rather than Qt3. Overall, a good day but I encountered some errors I did not experience with Qt3. ====================================================== tdebindings: Still a mess! These are typical errors --- too many to post, but similar to those when building against Qt3. DCOP.xs:29:20: error: qpoint.h: No such file or directory DCOP.xs:30:19: error: qrect.h: No such file or directory DCOP.xs:31:21: error: qregexp.h: No such file or directory DCOP.xs:32:19: error: qsize.h: No such file or directory DCOP.xs:33:25: error: qstringlist.h: No such file or directory In file included from DCOP.xs:35: /opt/trinity/include/dcopclient.h:26:22: error: tqobject.h: No such file or directory /opt/trinity/include/dcopclient.h:27:23: error: tqcstring.h: No such file or directory /opt/trinity/include/dcopclient.h:28:25: error: tqvaluelist.h: No such file or directory /opt/trinity/include/dcopclient.h:29:22: error: tqstring.h: No such file or directory In file included from /opt/trinity/include/dcopclient.h:30, from DCOP.xs:35: /opt/trinity/include/kdatastream.h:4:26: error: tqdatastream.h: No such file or directory In file included from /opt/trinity/include/dcopclient.h:31, from DCOP.xs:35: /opt/trinity/include/tdelibs_export.h:27:22: error: tqglobal.h: No such file or directory In file included from /opt/trinity/include/dcopclient.h:30, from DCOP.xs:35: /opt/trinity/include/kdatastream.h:23: error: expected initializer before '&' token /opt/trinity/include/kdatastream.h:32: error: expected initializer before '&' token /opt/trinity/include/kdatastream.h:40: error: expected initializer before '&' token /opt/trinity/include/kdatastream.h:49: error: expected initializer before '&' token ====================================================== Darrell

13 years, 2 months

Built on qt3 currently -- which dbus? dbus-1-qt3 or dbus-1-tqt and dbus-tqt

by David C. Rankin

Guys, Building from git (based on Qt3 currently) I have gotten to dbus, but now I'm confused on which dbus-1 I need. In tde-packaging for arch there is: trinity-dbus-1-qt3 trinity-dbus-tqt trinity-dbus-tqt-1 I originally thought that trinity-dbus-1-qt3 would fit my build since I used the Qt3 source from git, but there is no source for it in the tde/main/dependencies tree for trinity-dbus-1-qt3. What to do? Will the dbus-tqt files work when built on top of Qt3 instead of TQt3? -- David C. Rankin, J.D.,P.E.

13 years, 2 months

k3b, koffice not building for me

by Jay

Ok so i have successfully compiled the base of Trinity using Qt3 and everything in /usr. A while back i also successfully compiled many of the 'applications' from the applications folder. Today i am having no such luck. I am pushing out a release candidate of Porteus this weekend with a 'skin & bones' version of Trinity that successfully compiled a few weeks ago. The problem is that koffice is no longer compiling for me, and neither is k3b. I have booted using the Trinity-3.5.13 that i compiled and when trying to build k3b, here is my output. In file included from k3bglobals.cpp:28:0: /usr/include/tdeversion.h:57:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:64:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:71:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:78:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:84:5: error: ‘TDECORE_EXPORT’ does not name a type k3bglobals.cpp: In function ‘KIO::filesize_t K3b::imageFilesize(const KURL&)’: k3bglobals.cpp:304:126: warning: ‘static bool KIO::NetAccess::exists(const KURL&, bool)’ is deprecated (declared at /usr/include/kio/netaccess.h:282) k3bglobals.cpp: In function ‘bool K3b::mount(K3bDevice::Device*)’: k3bglobals.cpp:601:74: warning: converting ‘false’ to pointer type for argument 1 of ‘QString::QString(const char*)’ make[3]: *** [k3bglobals.lo] Error 1 make[3]: Leaving directory `/tmp/k3b/libk3b/core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/k3b/libk3b' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/k3b' make: *** [all] Error 2 Hoping someone more intelligent than i can point m in the right direction. J

13 years, 2 months

How to build one package component only

by Darrell Anderson

Every package has a doc directory containing the documentation files. How do I build only that directory as a mini package? Reason: All Trinity documentation is contained in Docbook files. DocBook is a markup language. Quanta Plus and Kate provide no mechanism to view the final result because all Docbook files have to be converted to another form for viewing. As I revise the various docbook files, I want to regularly view the results in a Trinity desktop. I want to do this quickly without building an entire package. Side note: Basically, this is the beginning of a discussion about creating an efficient Docbook editing environment, which I'll post to the wiki. If you have any experience or interest in the development side of Docbook then please feel welcome to help. You don't have to write or edit, just help set up the environment and I'll document the process for everybody --- but I need help getting there. :) Thanks! Darrell

13 years, 2 months

Need image conversion help

by Darrell Anderson

Okay artists, please help! I'm working on the TDE user guide. I need some image conversion help. I want to convert some 24-bit PNG images to "locolor." What does "locolor" mean? These are not icons but full images, in case that makes a difference. Is there a definition somewhere of "locolor"? How do I convert/save a 24-bit image as "locolor"? Of all of the various TDE image viewers, how do I view an image's properties to learn about the color depth, etc.? I have tried several (kolourpaint, krita, showfoto, gwenview). I am missing the big picture altogether, probably because I don't know the terminology. Thanks! Darrell

13 years, 2 months

Arch - pkgbuild tarball for git qt3 w/patchfile updated for latest qt3

by David C. Rankin

Calvin, Baho, Pawel, I have a tarball with the PKGBUILD, install and updated patches file for qt3 in git here: http://www.3111skyline.com/dl/dt/trinity/arch/git/trinity-qt3-git.tar.gz 2 patches were removed from qt-patches.tar.bz2 The git source 'dependencies-qt3' was created with the automated .tar.gz creation script which essentially did: cd tde/main/dependencies tar -czf dependencies-qt3.tar.gz qt3/ I don't think I have commit privileges on the trinity-packaging git repo. I did on svn, but don't with git that I know of. Tim, what do I need to do to get commit privileges for the arch repo? -- David C. Rankin, J.D.,P.E.

13 years, 2 months

Success! tqtinterface builds Fine on Arch from git

by David C. Rankin

Guys, One small build for a man, and one giant leap for Arch packages building from git :) After finally getting the cmake and admin directories populated, tqtinterface guilt without issue from the latest git! The first proud package: trinity-tqtinterface-3513-4-x86_64.pkg.tar.xz If the rest of the tree goes as well, this should be a timely breeze (loud knocking on wood). I have created tarballs from the git tree and they seem to be working fine building in an archroot. Do we have a tally as to home much of tde should be building at this time from the git tree? I saw Samelaine's announcement saying the packages were all done - does this mean I could start now and conceivably build a majority of tde? First looks -- look good! -- David C. Rankin, J.D.,P.E.

13 years, 2 months

Publishing help files, user guides, etc.

by Darrell Anderson

To cmake and makefile gurus: My plan is that starting with R14 the version number and copyright date of all Trinity documentation (help files, user guides, etc.) will be the same as the software release. That way the help files and guides look current rather than look 10 years old. By matching the release date and version, users know which release the documentation belongs and is an indication the documentation is not stagnant with a dumb version number like 0.1. I will create two entity variables that all related docbook files will use: release date and release version. Therefore the only place we need to update anything would be the entity file and not every single docbook file (ugh). The entity files are part of the tdelibs package. During the build process is there a way to automatically update these entity variables? I could do that in my own build scripts but I prefer a method that is global to any packager. How this would work: When a person builds from GIT today and then opens a handbook help file, the date would be today and the release would be R14.0.0 [DEVELOPMENT]. That way all drafts of all documentation show the current date and release number. However, when [DEVELOPMENT] is not part of the version string, that is, with an official release, then the date and release number are always hard-coded to the official release date. The release version is embedded in the TDE_VERSION_STRING variable in tdelibs/tdecore/tdeversion.h. I don't know whether the release date is hard-coded anywhere. Possibly when detecting that [DEVELOPMENT] is not part of the TDE_VERSION_STRING string, then the release date becomes the file date stamp of tdeversion.h. I'm just speculating and thinking out loud. Is this possible? Darrell

13 years, 2 months

Arch Builders - shadow updates break kdm - link to patched src provided

by David C. Rankin

Calvin, Pawel, Baho, The update to shadow 5 will break kdm do to a soname bump in libshadow. I have built a new source package with updated PKGBUILD for the old version and updated the pkgrel to 6. Grab the src tarball here: http://www.3111skyline.com/dl/dt/trinity/arch/src/shadow_4.1.4.3-6.tar.gz The only change was to the PKGBUILD. -- David C. Rankin, J.D.,P.E.

13 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels