[ 88%] Building CXX object
languages/cpp/debugger/CMakeFiles/libkdevdebugger-module.dir/memviewdlg.cpp.o
In file included from /opt/qt/include/qobject.h:42:0,
from /opt/qt/include/tqt/tqobject.h:32,
from /opt/qt/include/tqt/tqiodevice.h:26,
from /opt/qt/include/tqt/tqdatastream.h:26,
from /opt/qt/include/tqt/tqcstring.h:27,
from /opt/qt/include/tqt/tqstring.h:26,
from
/trinity.source/kdevelop/languages/cpp/debugger/mi/gdbmi.h:25,
from
/trinity.source/kdevelop/languages/cpp/debugger/memviewdlg.h:19,
from
/trinity.source/kdevelop/languages/cpp/debugger/memviewdlg.cpp:16:
/opt/qt/include/qobjectdefs.h: In function 'T qt_cast(const QObject*)
[with T = KHE::BytesEditInterface*]':
/opt/trinity/include/khexedit/byteseditinterface.h:162:51:
instantiated from 'KHE::BytesEditInterface* KHE::bytesEditInterface(T*)
[with T = QWidget]'
/trinity.source/kdevelop/languages/cpp/debugger/memviewdlg.cpp:287:55:
instantiated from here
/opt/qt/include/qobjectdefs.h:173:64: error: 'class
KHE::BytesEditInterface' has no member named 'staticMetaObject'
make[2]: ***
[languages/cpp/debugger/CMakeFiles/libkdevdebugger-module.dir/memviewdlg.cpp.o]
Error 1
make[1]: ***
[languages/cpp/debugger/CMakeFiles/libkdevdebugger-module.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 88%] Building CXX object
languages/php/CMakeFiles/libkdevphpsupport-module.dir/phpparser.cpp.o
[ 88%] Building CXX object
languages/php/CMakeFiles/libkdevphpsupport-module.dir/phpnewclassdlgbase.cpp.o
[ 88%] Building CXX object
languages/php/CMakeFiles/libkdevphpsupport-module.dir/phpnewclassdlg.cpp.o
[ 88%] Building CXX object
languages/php/CMakeFiles/libkdevphpsupport-module.dir/phpfile.cpp.o
Linking CXX shared module libkdevphpsupport.so
[ 88%] Built target libkdevphpsupport-module
make: *** [all] Error 2
Aborting...
From building kdellibs
Part 0
-- Looking for X11/extensions/Xrandr.h
-- Looking for X11/extensions/Xrandr.h - found
-- Looking for X11/extensions/XShm.h
-- Looking for X11/extensions/XShm.h - not found
find . -name Xrandr.h
/usr/include/X11/extensions/Xrandr.h
find . -name XShm.h
./usr/include/X11/extensions/XShm.h
Finds Xrandr.h but doesn't find XShm.h
As one sees they are both there
Part 1
-- checking for one of the modules 'freetype2'
-- checking for one of the modules 'fontconfig'
-- checking for one of the modules 'xrandr'
-- checking for one of the modules 'xrender'
-- checking for one of the modules 'libxml-2.0'
-- checking for one of the modules 'libxslt'
-- checking for one of the modules 'glib-2.0'
-- checking for one of the modules 'gobject-2.0'
Would these return a found status?
How are you folks getting QT3 and QT4 to coexist together and to ensure KDE4 finds QT4 and not QT3 and 3.5.10 or Trinity find QT3 and not QT4?
I'm looking at the latest Slackware release. Looks like the QT4 location is defined by the QT4DIR environment variable and not QTDIR. That is good news.
Another difference is in the KDE3 days, QTDIR pointed to /usr/lib/qt, which was a sym link to /usr/lib/qt-3.3.8b. In the latest Slackware release, the QT4 files are installed directly to /usr/lib/qt and there is no sym link.
If I understand correctly, when I build a QT3 package on a QT4 system, I should compile QT3 to install at /usr/lib/qt3 and then set a QTDIR environment variable to that location before compiling 3.5.10/Trinity packages.
Does this sound correct?
Darrell
I am getting the following error compiling kdebase svn
I have previously had no erorrs compiling kdebase
Some of my problems where dependences and I have fixed those but this
problem I am unable to correct
Thanks
29%] Building CXX object
kate/utils/CMakeFiles/kateutils-shared.dir/dockviewbase.cpp.o
Linking C executable kompmgr
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `add_damage':
kompmgr.c:(.text+0xee): undefined reference to `XFixesUnionRegion'
kompmgr.c:(.text+0x100): undefined reference to `XFixesDestroyRegion'
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `determine_mode':
kompmgr.c:(.text+0x2c4): undefined reference to `XFixesCreateRegion'
kompmgr.c:(.text+0x2dc): undefined reference to `XFixesCopyRegion'
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `win_extents':
kompmgr.c:(.text+0x7c6): undefined reference to `XFixesCreateRegion'
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `set_fade.clone.14':
kompmgr.c:(.text+0x13a9): undefined reference to `XFixesDestroyRegion'
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `run_fades':
kompmgr.c:(.text+0x16db): undefined reference to `XFixesDestroyRegion'
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `finish_unmap_win':
kompmgr.c:(.text+0x19a2): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x1a00): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x1a38): undefined reference to `XFixesDestroyRegion'
CMakeFiles/kompmgr.dir/kompmgr.c.o:kompmgr.c:(.text+0x1a70): more
undefined references to `XFixesDestroyRegion' follow
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `add_win':
kompmgr.c:(.text+0x1bd1): undefined reference to `XDamageCreate'
kompmgr.c:(.text+0x1c7b): undefined reference to `XShapeSelectInput'
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `finish_destroy_win':
kompmgr.c:(.text+0x1e1a): undefined reference to `XDamageDestroy'
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `repair_win':
kompmgr.c:(.text+0x1fc2): undefined reference to `XFixesCreateRegion'
kompmgr.c:(.text+0x1ff1): undefined reference to `XDamageSubtract'
kompmgr.c:(.text+0x2010): undefined reference to `XFixesTranslateRegion'
kompmgr.c:(.text+0x2076): undefined reference to `XDamageSubtract'
kompmgr.c:(.text+0x2094): undefined reference to `XFixesCreateRegion'
kompmgr.c:(.text+0x20a7): undefined reference to `XFixesCopyRegion'
kompmgr.c:(.text+0x20ca): undefined reference to `XFixesTranslateRegion'
kompmgr.c:(.text+0x20e1): undefined reference to `XFixesUnionRegion'
kompmgr.c:(.text+0x20f0): undefined reference to `XFixesDestroyRegion'
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `border_size':
kompmgr.c:(.text+0x2138): undefined reference to
`XFixesCreateRegionFromWindow'
kompmgr.c:(.text+0x216b): undefined reference to `XFixesTranslateRegion'
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `paint_all':
kompmgr.c:(.text+0x21d1): undefined reference to
`XFixesSetPictureClipRegion'
kompmgr.c:(.text+0x2361): undefined reference to
`XFixesSetPictureClipRegion'
kompmgr.c:(.text+0x241b): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x2504): undefined reference to `XFixesIntersectRegion'
kompmgr.c:(.text+0x252f): undefined reference to
`XFixesSetPictureClipRegion'
kompmgr.c:(.text+0x25cd): undefined reference to
`XFixesSetPictureClipRegion'
kompmgr.c:(.text+0x265e): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x2693): undefined reference to
`XFixesSetPictureClipRegion'
kompmgr.c:(.text+0x272c): undefined reference to `XFixesIntersectRegion'
kompmgr.c:(.text+0x2757): undefined reference to
`XFixesSetPictureClipRegion'
kompmgr.c:(.text+0x2827): undefined reference to
`XFixesSetPictureClipRegion'
kompmgr.c:(.text+0x2b28): undefined reference to
`XFixesSetPictureClipRegion'
kompmgr.c:(.text+0x2b6d): undefined reference to `XFixesSubtractRegion'
kompmgr.c:(.text+0x2c36): undefined reference to `XFixesCreateRegion'
kompmgr.c:(.text+0x2c52): undefined reference to `XFixesCopyRegion'
kompmgr.c:(.text+0x2e51): undefined reference to `XFixesCreateRegion'
kompmgr.c:(.text+0x2f12): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x2f41): undefined reference to `XFixesSubtractRegion'
kompmgr.c:(.text+0x30b5): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x30d0): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x3103): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x3136): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x32ce): undefined reference to `XFixesCreateRegion'
kompmgr.c:(.text+0x3306): undefined reference to `XFixesIntersectRegion'
kompmgr.c:(.text+0x331d): undefined reference to
`XCompositeNameWindowPixmap'
CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `main':
kompmgr.c:(.text+0x414c): undefined reference to `XCompositeQueryVersion'
kompmgr.c:(.text+0x4181): undefined reference to `XDamageQueryExtension'
kompmgr.c:(.text+0x4265): undefined reference to `XFixesQueryExtension'
kompmgr.c:(.text+0x469d): undefined reference to
`XCompositeRedirectSubwindows'
kompmgr.c:(.text+0x4b42): undefined reference to `XFixesCreateRegion'
kompmgr.c:(.text+0x4bc2): undefined reference to `XFixesCreateRegion'
kompmgr.c:(.text+0x4be5): undefined reference to `XFixesCopyRegion'
kompmgr.c:(.text+0x4f15): undefined reference to `XFixesUnionRegion'
kompmgr.c:(.text+0x4f28): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x53d1): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x550e): undefined reference to `XFixesDestroyRegion'
kompmgr.c:(.text+0x5ab6): undefined reference to
`XCompositeRedirectSubwindows'
kompmgr.c:(.text+0x5afb): undefined reference to `XShapeQueryExtension'
collect2: ld returned 1 exit status
make[2]: *** [kwin/kompmgr/kompmgr] Error 1
make[1]: *** [kwin/kompmgr/CMakeFiles/kompmgr.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 29%] Building CXX object
kate/utils/CMakeFiles/kateutils-shared.dir/messageview.cpp.o
[ 29%] Building CXX object
kate/utils/CMakeFiles/kateutils-shared.dir/listboxview.cpp.o
Linking CXX shared library libkateutils.so
[ 29%] Built target kateutils-shared
make: *** [all] Error 2
Aborting...
I don't know what happened. I modified my build scripts to install Trinity in /opt/trinity. I was planning to install Trinity alongside 3.5.10, which is installed in /usr. This is part of my preparation for building on newer Slackware systems.
Here is the tail end of the build log:
======================================
(cd .libs && rm -f libgmcop.la && ln -s ../libgmcop.la libgmcop.la)
make[2]: Leaving directory `/dev/shm/dependencies/arts/gmcop'
Making all in qtmcop
make[2]: Entering directory `/dev/shm/dependencies/arts/qtmcop'
/usr/lib/qt/bin/moc ./qiomanager_p.h qiomanager_p.moc
Qt meta object compiler
moc: Too many input files specified
Usage: moc [options] <header-file>
-o file Write output to file rather than stdout
-f[file] Force #include, optional file name
-p path Path prefix for included file
-i Do not generate an #include statement
-k Do not stop on errors
-nw Do not display warnings
-v Display version of moc
make[2]: *** [qiomanager_p.moc] Error 1
make[2]: Leaving directory `/dev/shm/dependencies/arts/qtmcop'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/dev/shm/dependencies/arts'
make: *** [all] Error 2
======================================
Several days ago I built 3.5.12 with no failures. So I did something wrong, but I don't know what.
This is a repeatable failure. I checked that I have qt-3.3.8b installed and not 3.3.8c. Automake is the correct version. tqtinterface-3.5.12 builds without errors and is installed in /usr.
Thanks.
Darrell
Also I can work some magic in gimp and make some abstract color backgrounds and such
Calvin Morrison
Kristopher Gamrat <pikidalto(a)gmail.com> wrote:
>I personally have no opinion either way. I will add in a few comments though:
>
>If it is a legal issue, we should change the artwork and branding. I'm
>not too familiar with the Creative Commons licenses, but if they
>prevent us from reusing the artwork and KDE e.V. decides to kick us,
>we'll need to replace it regardless, so it would be wise to have stuff
>ready regardless.
>
>When most people think of rebranding, they think of both the names of
>the apps and the artwork, or at least most of the people I know
>(myself included). If it is just the artwork, we should say "artwork
>rebranding" instead of just "rebranding".
>
>For the artwork, I can go around with my camera and take pics of some
>of the scenary in my area. While I don't particularly like the scenary
>here, a lot of people do. I personally don't care for a bunch of tall,
>lighted buildings in a blur of smog, but apparently that is popular
>(I've heard so many people say, "Ooh, that is so pretty!" when driving
>into town at night). Buildings aren't the only pics I can get. While
>it's too late to get a snow covered landscape (spring finally arrived
>after weeks of unpredictable weather), I can get some spring and
>summer stuff, and maybe autumn if we're still working on the artwork.
>I'm no good with photo editing and imposing pics and logos on top of
>other images, so someone else would have to do it, but I can still
>send some stuff in.
>
>--
>Kris
>"Piki"
>Ark Linux Webmaster
>Trinity Desktop Environment Packager
>
>---------------------------------------------------------------------
>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
>
(Repost: originally posted as a reply creating broken thread to "Re:
[trinity-devel] [Win+] shortcut default proposal - Efficient Desktop
Manipulation". Posted again to insure proper threading)
---------Original---------
This got missed at the meeting, so it's getting announced here: an initial
mascot and logo proposal.
The mascot doesn't have a name right now, just a cryptic designation of L315 so
it can be referred to as something until it has earned a name.
It represents the user's individual TDE installation, typically customized to
that user's needs, and as such, can be found in multiple strange configurations
and doing various things.
The Etherpad page is here:
http://trinity.etherpad.trinitydesktop.org/8
If you just want to look at a quick single image, here's L315 playing a game
with an Atari 2600 joystick: http://imagebin.org/143362 -- this is my second
favorite image so far.
I may add the plain image of L315 standing at attention at some point, but I'm
wondering if a better default pose is possible.
This includes a few situations and configurations of L315, and at the bottom
shows three applications of a simple and efficient logo derived from L315.
Logos need to be as simple as possible, and this one qualifies as simple, and is
directly tied to L315. My main worry is that there might be someone else with a
nearly identical logo that I don't know about.
What I need from you: nits with the implementation of the concept, with L315's
configuration, with the logo in the three icon ideas, and possibly with the
entire base idea I'm working with. Suggestions for improving the artwork only
apply if you have immediately fallen in love with L315. 8)
Important thing to remember: Failed branding mascots are by definition
forgettable. We want to to be memorable.
James Gholston
---------End Original---------
I also tossed out the idea of a Phoenix as a logo/mascot "A phoenix dies a fiery
death but then rises again from the ashes." A good KDE3-Trinity analogy. (plus a
pretty cool looking logo)
A few ideas (for discussion only) I has many forms. The more abstract -- the better:
http://www.tchan.de/bilder/phoenixgross.gifhttp://davidalves.net/images/robocode/phoenix3.jpghttp://www.sightquest.com/images/cat/phoenixbird.jpghttp://pegasus.cc.ucf.edu/~torrey/phoenix.gifhttp://affiliates.art.com/get.art?T=15043079&A=028615&L=8&P=12617687&S=2&Y=0http://www.crimsonmonkey.com/phoenix.jpghttp://t2.gstatic.com/images?q=tbn:ANd9GcS0Hr9P3nN8WTDzVAPx8O9a6yO--aCBsxhJ…http://hornconcerto.net/wp-content/uploads/2009/07/phoenix_force.jpg
--
David C. Rankin, J.D.,P.E.
