kdevelop CVS doesn't compile with KDE CVS

Joseph Davidson jdavidso at vt.edu
Fri Oct 10 21:10:06 UTC 2003


I'm seeing this same problem... it is looking for a non-existant  
kdockwidget_p.h  Is there a fix for this?

--
Joe



On Sep 20, 2003, at 5:29 PM, Nicholas Brown wrote:

> I'm seeing the below error;
>
> make[4]: Entering directory  
> `/home/kdedevel/kdecvs/build/kdevelop/lib/qextmdi/sr
> c'
> if /bin/sh ../../../libtool --silent --mode=compile --tag=CXX g++  
> -DHAVE_CONFIG_
> H -I. -I../../../../../source/kdevelop/lib/qextmdi/src -I../../..  
> -I../../../../
> ../source/kdevelop/lib/qextmdi/include  
> -I../../../../../source/kdevelop/lib/qext
> mdi/res -I../../../../../source/kdevelop/lib/structure  
> -I/home/kdedevel/kdecvs/i
> nstall/include -I/usr/X11R6/include   -DQT_THREAD_SUPPORT   
> -D_REENTRANT  -Wnon-v
> irtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith  
> -Wwrite-strings -ans
> i -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion  
> -Wchar-subscripts
> -fno-builtin -g -O2 -Wformat-security -Wmissing-format-attribute  
> -fno-exceptions
>  -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST  
> -DQT_NO_STL
> -DQT_NO_COMPAT -DQT_NO_TRANSLATION  -MT kmdichildfrm.lo -MD -MP -MF  
> ".deps/kmdic
> hildfrm.Tpo" \
>   -c -o kmdichildfrm.lo `test -f  
> '../../../../../source/kdevelop/lib/qextmdi/src
> /kmdichildfrm.cpp' || echo  
> '../../../../../source/kdevelop/lib/qextmdi/src/'`../
> ../../../../source/kdevelop/lib/qextmdi/src/kmdichildfrm.cpp; \
> then mv ".deps/kmdichildfrm.Tpo" ".deps/kmdichildfrm.Plo"; \
> else rm -f ".deps/kmdichildfrm.Tpo"; exit 1; \
> fi
> In file included from  
> ../../../../../source/kdevelop/lib/qextmdi/include/kmdimai
> nfrm.h:49,
>                  from  
> ../../../../../source/kdevelop/lib/qextmdi/src/kmdichildfr
> m.cpp:44:
> ../../../../../source/kdevelop/lib/qextmdi/include/kmdidockwidget.h: 
> 23:28: kdock
> widget_p.h: No such file or directory
> In file included from  
> ../../../../../source/kdevelop/lib/qextmdi/include/kmdimai
> nfrm.h:49,
>                  from  
> ../../../../../source/kdevelop/lib/qextmdi/src/kmdichildfr
> m.cpp:44:
> ../../../../../source/kdevelop/lib/qextmdi/include/kmdidockwidget.h: 
> 73: base cla
> ss `KDockContainer' has incomplete type
> ../../../../../source/kdevelop/lib/qextmdi/include/kmdidockwidget.h:  
> In construc
> tor `KMdiDockContainerBase::KMdiDockContainerBase()':
> ../../../../../source/kdevelop/lib/qextmdi/include/kmdidockwidget.h: 
> 75: type `st
> ruct KDockContainer' is not a direct base of `KMdiDockContainerBase'
> In file included from  
> ../../../../../source/kdevelop/lib/qextmdi/src/kmdichildfr
> m.cpp:44:
> ../../../../../source/kdevelop/lib/qextmdi/include/kmdimainfrm.h:362: 
> 2: warning:
>  #warning fixme
> make[4]: *** [kmdichildfrm.lo] Error 1
> make[4]: Leaving directory  
> `/home/kdedevel/kdecvs/build/kdevelop/lib/qextmdi/src
> '
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory  
> `/home/kdedevel/kdecvs/build/kdevelop/lib/qextmdi'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/kdedevel/kdecvs/build/kdevelop/lib'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/kdedevel/kdecvs/build/kdevelop'
> make: *** [all] Error 2
>
>
> The problem code in kmdidockwidget.h appears to be;
> <snip>
> #if defined(KDE_MAKE_VERSION)
> # if KDE_VERSION < KDE_MAKE_VERSION(3,1,90)
> #  ifndef OLDER_THAN_KDE_3_2
> #   define OLDER_THAN_KDE_3_2
> #  endif
> # endif
> #else
> # define OLDER_THAN_KDE_3_2
> #endif
>
> #if defined(NO_KDE) || defined(OLDER_THAN_KDE_3_2)
> # include <kdockwidget_compat.h>
> using namespace KDockWidget_Compat;
> #else
> # include <kdockwidget.h>
> # include <kdockwidget_p.h>
> #endif
> <snip>
>
> KDE CVS is at version higher than 3.1.90;
>
> [bash]$ kde-config --version
> Qt: 3.2.1
> KDE: 3.1.91 (CVS >= 20030907)
> kde-config: 1.0
> [bash]$
>
> But this KDE CVS does not install kdockwidget_p.h due to the change  
> made in kdelibs/kdeui/Makefile.am
> revision 1.310
> "Remove private header from installation. It had been marked as don't  
> use anyways and was only needed for kate"
>
> I think someone needs to fix kdevelop. Should I create a bug report  
> for this? (ie what are the rules for bugs in cvs code?)
>
> thanks,
> Nick
>
>
> _______________________________________________
> Kdevelop-devel mailing list
> Kdevelop-devel at barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>





More information about the KDevelop-devel mailing list