build failure in kdebase

[Benjamin Reed]

Craig Drummond wrote:

> I've changed this - please update! The .c file is now compiled sperately. This 
> is a different issue to the CXConfig symbols issue.

Yeah, GetPid.c is fine, but I still get these build errors:

---(snip!)---
/bin/sh ../../../libtool --silent --mode=compile --tag=CXX g++-3.3 
-DHAVE_CONFIG_H -I. -I. -I../../.. -I/sw/include/freetype2 -I/sw/include 
-I/usr/X11R6/include -DOS_ -I./../../fo
nts -I/sw/include -I/sw/include/qt -I/usr/X11R6/include  -I/sw/include 
-DQT_THREAD_SUPPORT -no-cpp-precomp -fno-common -I/sw/include 
-I/sw/include  -Wnon-virtual-dtor -Wno-long-l
ong -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -Os -fno-exceptions 
-fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST 
-DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRAN
SLATION -D_GNU_SOURCE  -c -o XConfig.lo `test -f 'XConfig.cpp' || echo 
'./'`XConfig.cpp
XConfig.cpp:60: error: prototype for `bool CXConfig::configureDir(const
    QString&)' does not match any in class `CXConfig'
XConfig.h:100: error: candidate is: static bool 
CXConfig::configureDir(const
    QString&, QStringList&)
XConfig.cpp: In member function `bool CXConfig::configureDir(const 
QString&)':
XConfig.cpp:62: error: no matching function for call to `CXConfig::
    createFontsDotDir(const QString&)'
XConfig.h:132: error: candidates are: static bool
    CXConfig::createFontsDotDir(const QString&, QStringList&)
XConfig.cpp: At global scope:
XConfig.cpp:883: error: prototype for `bool 
CXConfig::createFontsDotDir(const
    QString&)' does not match any in class `CXConfig'
XConfig.h:132: error: candidate is: static bool
    CXConfig::createFontsDotDir(const QString&, QStringList&)
make: *** [XConfig.lo] Error 1
---(snip!)---

>>Seems like if 2 parts of the project are using kxftconfig it should be
>>factored into something both can include...
> 
> 
> why? Works fine for me. After all, most of KDE #includes the .moc files - and 
> these are just C++ files. Anyway the problem is in XConfig.cpp/h - not 
> kxftconfig.cpp

Sure, they're also autogenerated, and aren't used across build 
directories.  Just seems that it would be cleaner...  I don't care, 
really, as long as it works, just seems like not having to work around 
it like that would make it easier on you too...

-- 
Benjamin Reed a.k.a. Ranger Rick -- http://ranger.befunk.com/
gpg: 6401 D02A A35F 55E9 D7DD  71C5 52EF A366 D3F6 65FE
"You can scoff, Lister, that's nothing new.  They laughed at Galileo.
They laughed at Edison.  They laughed at Columbo."   "Who's Columbo?"
"The man with the dirty mac who discovered America."   -- _Red Dwarf_

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 253 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20031031/f85ff71e/attachment.sig>