[prev in list] [next in list] [prev in thread] [next in thread]
List: pykde
Subject: Re: [PyKDE] PyKDE compling woes with current snapshots
From: Jim Bublitz <jbublitz () nwinternet ! com>
Date: 2003-04-24 14:42:05
[Download RAW message or body]
On 24-Apr-03 Hans-Peter Jansen wrote:
> On Thursday 24 April 2003 08:32, Gordon Tyler wrote:
>>
>> Now I've run into a compile error that has me stumped:
>>
>> sipkpartsKPartsPart.cpp: In method `void
>> sipKParts_MainWindow::setInstance(KInstance *)':
>> sipkpartsKPartsPart.cpp:1817: no matching function for call to
>> `sipKParts_PartBase::sipVH_setInstance (sipMethodCache *,
>> sipThisType
>> *&, KInstance *&)'
>> sipkpartsKPartsPartBase.h:59: candidates are: static void
>> sipKParts_PartBase::sipVH_setInstance(const sipMethodCache *,
>> sipThisType *, KInstance *, bool)
>> sipkpartsKPartsFactory.cpp: In method `void
>> sipKParts_DockMainWindow::setInstance(KInstance *)':
>> sipkpartsKPartsFactory.cpp:2363: no matching function for call
>> to
>> `sipKParts_PartBase::sipVH_setInstance (sipMethodCache *,
>> sipThisType
>> *&, KInstance *&)'
>> sipkpartsKPartsFactory.cpp:1723: candidates are: static void
>> sipKParts_PartBase::sipVH_setInstance(const sipMethodCache *,
>> sipThisType *, KInstance *, bool)
>>
>> Any ideas?
>
> Blind guess: doesn't this relate to missing ampersands, Phil
> mentioned lately?
There are no ampersands in the subject code.
> This would imply, that at least the bool arg has a default
> value.
Mo, it doesn't.
> Which KDE version you bind against?
I believe this is the same in any version.
Jim
_______________________________________________
PyKDE mailing list PyKDE@mats.gmd.de
http://mats.gmd.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic