'Re: bug in activity.cpp?'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: bug in activity.cpp?
From:       patrick flaherty <patf () well ! com>
Date:       2010-05-26 23:49:42
Message-ID: 4BFDB396.9090502 () well ! com
[Download RAW message or body]

On 5/26/2010 3:19 PM, Michael Jansen wrote:
> On Mittwoch 26 Mai 2010 21:59:39 patrick flaherty wrote:
>    
>> On 5/26/2010 10:11 AM, Michael Jansen wrote:
>>      
>>>>> [ 50%] Building CXX object
>>>>> workspace/plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/ac
>>>>> ti vity.o cd
>>>>> /home/kde-devel/kde/build/trunk/KDE/kdebase/workspace/plasma/desktop/sh
>>>>> el l&&   /usr/bin/c++   -Dkdeinit_plasma_desktop_EXPORTS -D_BSD_SOURCE
>>>>> -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DQT_NO_STL -DQT_NO_CAST_TO_ASCII
>>>>> -D_REENTRANT -DKDE_DEPRECATED_WARNINGS -DHAVE_CONFIG_H=1
>>>>> -DKDE_DEFAULT_DEBUG_AREA=1204 -Wnon-virtual-dtor -Wno-long-long -ansi
>>>>> -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith
>>>>> -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new
>>>>> -fno-common -Woverloaded-virtual -fno-threadsafe-statics
>>>>> -fvisibility=hidden -fvisibility-inlines-hidden -O2 -g -DNDEBUG
>>>>> -DQT_NO_DEBUG -fPIC
>>>>> -I/home/kde-devel/kde/build/trunk/KDE/kdebase/workspace/plasma/desktop/
>>>>> sh ell
>>>>> -I/home/kde-devel/kde/sources/trunk/KDE/kdebase/workspace/plasma/deskto
>>>>> p /shell -I/home/kde-devel/kde/sources/trunk/KDE/kdebase
>>>>> -I/home/kde-devel/kde/build/trunk/KDE/kdebase
>>>>> -I/home/kde-devel/kde/build/trunk/KDE/kdebase/workspace
>>>>> -I/home/kde-devel/kde/sources/trunk/KDE/kdebase/workspace/kdm
>>>>> -I/home/kde-devel/kde/sources/trunk/KDE/kdebase/workspace/libs
>>>>> -I/home/kde-devel/kde/sources/trunk/KDE/kdebase/workspace/libs/kworkspa
>>>>> ce
>>>>> -I/home/kde-devel/kde/sources/trunk/KDE/kdebase/workspace/libs/plasmag
>>>>> ene ricshell
>>>>> -I/home/kde-devel/kde/sources/trunk/KDE/kdebase/workspace/plasma/shells
>>>>> / common
>>>>> -I/home/kde-devel/kde/sources/trunk/KDE/kdebase/workspace/plasma/deskto
>>>>> p /shell/scripting
>>>>> -I/home/kde-devel/kde/sources/trunk/KDE/kdebase/workspace/libs/kephal
>>>>> -I/usr/include/KDE -I/usr/include/QtXmlPatterns -I/usr/include/QtXml
>>>>>
>>>>>            
>>>           ^^^^^^^^^^
>>>
>>> That look s wrong. Where did you install your trunk kdelibs build
>>>
>>> Mike
>>>        
>> Hi Mike,
>>
>> Install my trunk kdelibs build?  I don't remember doing that.
>>      
> You did. cmakekde is doing that for you. Most likely you installed somewhere into you $HOME
> directory.
>
>    
Thanx again for you help Mike.

The cmakede's ... yes I did those.  As I understood it, the cmakeke's 
set up the necessary files under build based on what I'd downloaded via 
svn into source.

kde-devel $HOME as the instructions suggest.
>> The KDE
>> that was running was what came originally with openSUSE11.2 - which I
>> think was KDE 4.3.  I use the past tense because one of the steps here
>> (the instructions I've been following for the exercise):
>>
>> http://en.opensuse.org/KDE/Developing/Guide
>>
>> upgraded the installation to 4.4.76.
>>      
> Just had a look and yes your installation was updated at the "Install Software needed for KDE 4
> step".
>
>
>    
>> I've looked around and while I've found various KDE libraries in
>> production locations, I confess that I haven't found a single location
>> that I think corresponds to the running KDE installation.
>>      
> I don't really understand you here but i guess your problem is the following. The recipe provides
> two scripts. kde4-run-env and kde4-build-env. Whenever you want to work on the kde4 development
> front you have to issue ". kde4-build-env" first and THEN do it. ALWAYS.
>
>    
I (at least now) understand well the difference between kde4-build-env 
and kde4-run-env.  I may though, much earlier, have run kde4-run-env 
once and that may have screwed thing up (don't remember).
> I guess you configured your kdebase checkout while having the kde4-run-env active. You have two
> possibilities to prevent that from happening:
>
> 1. Open yast and remove all kde-devel packages (kdebase(4?)-devel, kdelibs(4?)-devel ...). If you
> plan to compile that stuff yourself anyway you don't need it. And as you just learned it will make
> your day miserable when you forget to switch to the correct environment.
>
> 2. Work in a virtual machine if your workstation can handle it. Just install a xfce desktop or
> "konsole login" only package selection and compile kde yourself there. Is a bit harder.
>
>
>
> Mike
>
>
>    
I am working in a virtual machine.

I wiped things out again and started over.

Another possible source of problems:

http://en.opensuse.org/KDE/Developing/Guide  (note that the techbase 
article takes one here for openSUSE).

'Install the KDE 4 development prerequisites'   (search for this on the 
page above).

This runs yast from here:

http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Desktop/openSUSE_11.2/KDE4-DEVEL.ymp

Which sets up the unstable, devel stuff.  In particular, KDE UNSTABLE; 
Qt 4.6; and OpenSUSE:11.2:Update

The key point in the immediately above (for me), is that yast finds all 
kinds of Conflicts and I don't really know what options are best to 
choose (to resolve each conflict).

I've installed a 64 bit version of openSUSE 11.2 and yast finds that 
there are not, in many cases, x86_64 equivalent modules that I need.  
One thing it suggests is backing up to an x586 module in spite of 'the 
inferior architecture'.

Maybe it's not a good idea to try to build the KDE trunk in a 64 bit 
environment?

pat

>    
>> My working directories (not what you asked I think) are:
>>
>> kde-devel@linux-26qn:~/kde/build/trunk/KDE/
>> kde-devel@linux-26qn:~/kde/source/trunk/KDE/
>>
>> pat
>>      
>
>
>    

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread] 