> QXEmbed was causing build problems on some platforms - not sure
> of the details, but I imagine I thought no one was using it
> anyway and there might have been some questions about the code
> being usable in PyKDE in the first place.
It's quite usable. Definitely one of those "wow! it worked!
On Friday April 23 2004 01:43, Troy Melhase wrote:
> > Please report any build, compile or execution errors you run
> > across to the list.
> This is exciting. I upgraded all these today:
> Qt from 3.2 to 3.3
> KDE from 3.1.4 to 3.2.1
> SIP from 3.8 to 3.10.1
> PyQt from 3.8 to 3.11
> PyKDE from
On Friday April 23 2004 04:00, Torsten Marek wrote:
> Jim Bublitz schrieb:
> > The deprecation warnings are coming from KDE itself (from
> > the h files) I would think. I haven't seen them on my
> > compiles though. Right now I have that gcc feature
> > effectively #defined out when I generate th
On Friday April 23 2004 02:36, David Boddie wrote:
> On Fri, 23 Apr 2004 08:04:50, Simon Edwards
<[EMAIL PROTECTED]> wrote:
> > You da boss!
> > I got a clean compile, install, and importTest.py! :-)
> Same here! I'm beginning to think I should install a current
> Slackware release on my spare p
Jim Bublitz schrieb:
On Thursday April 22 2004 13:46, Torsten Marek wrote:
Jim Bublitz schrieb:
is it possible that it is impossible to build PyKDE using sip4
(latest snapshot)? I had to manually add some %Imports in the
mod.sip.in (sip complained, for instance, "sip: The
kfile module must expli
On Fri, 23 Apr 2004 08:04:50, Simon Edwards <[EMAIL PROTECTED]> wrote:
> You da boss!
>
> I got a clean compile, install, and importTest.py! :-)
Same here! I'm beginning to think I should install a current Slackware
release on my spare partition and make some packages.
> Thanks Jim,
Yes, nice o
> Please report any build, compile or execution errors you run
> across to the list.
This is exciting. I upgraded all these today:
Qt from 3.2 to 3.3
KDE from 3.1.4 to 3.2.1
SIP from 3.8 to 3.10.1
PyQt from 3.8 to 3.11
PyKDE from 3.7+hacks to 3.11
And even:
SciPy from 0.2_alpha_something to 0.
On Friday 23 April 2004 06:47, Jim Bublitz wrote:
> On Thursday April 22 2004 13:49, Simon Edwards wrote:
> > If it is Mandrake specific, then I can better just patch it
> > when I make the RPMs.
>
> Well, some people will probably want to compile against Mdk, so
> this needs to be least common d
On Thursday April 22 2004 13:49, Simon Edwards wrote:
> On Thursday 22 April 2004 22:26, Jim Bublitz wrote:
> > > I'll have a dig around here and try to find out where
> > > eventModuleName went.
> >
> > This looks like a case of "backporting". In the "official"
> > sources (from kde.org), eventMo
On Thursday April 22 2004 13:56, Mateusz Korniak wrote:
> On Wed, 21 Apr 2004, Jim Bublitz wrote:
> (...)
> I got stuck with:
>
> + python configure.py -d /usr/lib/python2.3/site-packages -n
> /usr/lib -v /usr/share/sip -c -j 3
>
> PyKDE version 3.11.0
>---
>
> Python include d
On Thursday April 22 2004 13:46, Torsten Marek wrote:
> Jim Bublitz schrieb:
> is it possible that it is impossible to build PyKDE using sip4
> (latest snapshot)? I had to manually add some %Imports in the
> mod.sip.in (sip complained, for instance, "sip: The
> kfile module must explicitly %Import
On Thursday April 22 2004 14:41, Steven Robson wrote:
class KConfigSkeletonItem
{
%TypeHeaderCode
#include
#include
%End
> I tried all that you suggested and got some more debug info,
> which I didn't really understand.
> (did "make clean", and then the same make command as before,
> to get the
On Thursday 22 April 2004 22:59, Jim Bublitz wrote:
> On Thursday April 22 2004 10:53, Steven Robson wrote:
> > I'm getting the build errors attached when building the
> > recently released PyKDE snapshot.
> > Other info:
> > Slackware 9.1, python 2.3.1, sip 3.10.1 (3.10.1-192),
> > PyQt-x11-gpl-3.
On Thursday April 22 2004 10:53, Steven Robson wrote:
> I'm getting the build errors attached when building the
> recently released PyKDE snapshot.
> Other info:
> Slackware 9.1, python 2.3.1, sip 3.10.1 (3.10.1-192),
> PyQt-x11-gpl-3.11.
>
> I did python configure.py -c
> followed by make > makeop
On Thursday 22 April 2004 21:47, Jim Bublitz wrote:
> On Thursday April 22 2004 10:53, Steven Robson wrote:
> > I'm getting the build errors attached when building the
> > recently released PyKDE snapshot.
> > Other info:
> > Slackware 9.1, python 2.3.1, sip 3.10.1 (3.10.1-192),
> > PyQt-x11-gpl-3.
On Thursday April 22 2004 10:53, Steven Robson wrote:
> I'm getting the build errors attached when building the
> recently released PyKDE snapshot.
> Other info:
> Slackware 9.1, python 2.3.1, sip 3.10.1 (3.10.1-192),
> PyQt-x11-gpl-3.11.
>
> I did python configure.py -c
> followed by make > makeop
On Wed, 21 Apr 2004, Jim Bublitz wrote:
(...)
I got stuck with:
+ python configure.py -d /usr/lib/python2.3/site-packages -n /usr/lib -v
/usr/share/sip -c -j 3
PyKDE version 3.11.0
---
Python include directory is /usr/include/python2.3
Python version is 2.3.3
sip version
On Thursday 22 April 2004 22:26, Jim Bublitz wrote:
> > I'll have a dig around here and try to find out where
> > eventModuleName went.
>
> This looks like a case of "backporting". In the "official"
> sources (from kde.org), eventModuleName() is in 3.2.0 but not
> 3.2.1 or greater.
Sounds abou
Jim Bublitz schrieb:
I'm finishing a couple of test builds for PyKDE-3.11alpha5 and
assuming those work OK, I'll be sending a tarball to Phil to put
up either on the PyKDE page or in a PyKDE snapshot directory.
This isn't the final release. It should build against any KDE
version from 3.0.0 thr
On Thursday April 22 2004 12:45, Simon Edwards wrote:
> On Thursday 22 April 2004 05:55, Jim Bublitz wrote:
> > I'm finishing a couple of test builds for PyKDE-3.11alpha5
> > and assuming those work OK, I'll be sending a tarball to
> > Phil to put up either on the PyKDE page or in a PyKDE
> > snaps
On Thursday 22 April 2004 05:55, Jim Bublitz wrote:
> I'm finishing a couple of test builds for PyKDE-3.11alpha5 and
> assuming those work OK, I'll be sending a tarball to Phil to put
> up either on the PyKDE page or in a PyKDE snapshot directory.
Yay!
This is what I got on Mandrake 10.0, KDE 3
I'm getting the build errors attached when building the recently released
PyKDE snapshot.
Other info:
Slackware 9.1, python 2.3.1, sip 3.10.1 (3.10.1-192), PyQt-x11-gpl-3.11.
I did python configure.py -c
followed by make > makeop 2>> makeop
Regards,
Steven
make[1]: Entering directory `/home/s
On Thursday April 22 2004 03:58, Hans-Peter Jansen wrote:
> Did you manage to fix the strange type errors in the
> *menudemo.py and possibly even the kurldemo.py issue, I
> reported 03/17 to you and Phil?
Yes - the menudemo problems occurred because the specific action
classes (like KToggleAction
On Thursday 22 April 2004 05:55, Jim Bublitz wrote:
> I'm finishing a couple of test builds for PyKDE-3.11alpha5 and
> assuming those work OK, I'll be sending a tarball to Phil to put
> up either on the PyKDE page or in a PyKDE snapshot directory.
Congrats.
> This isn't the final release. It shou
I'm finishing a couple of test builds for PyKDE-3.11alpha5 and
assuming those work OK, I'll be sending a tarball to Phil to put
up either on the PyKDE page or in a PyKDE snapshot directory.
This isn't the final release. It should build against any KDE
version from 3.0.0 through 3.2.1 inclusive.
25 matches
Mail list logo
