Trouble building wxPython

wxPython Users
#1

Hi Robin,
    I want to thank you for all the help you've provided. I think I've
been down all the roads I can try except the rpmbuild route.

    I grabbed and installed the wxPython for fc7 python2.5 with unicode rpm's.
    I rebuilt python2.5 to use --with-unicode=UCS4.

when I ran the demo.py program it ran displaying the window and interior
briefly
then crashing with a X11 error BAD_PARAMETER. In this mode I can import wx but

as soon as I try to display anything it crashes with the above error.

    I'm confused about the advice you gave in your last email. You suggested:

Have you tried making your own RPMs with rpmbuild as I suggested in the
other mail? It really will take care of everything for you and you
won't have to worry about any of this. You'll just have to install the
RPMs it produces. They will include wxWidgets and wxPython and will be
built for the Python on your system.

    I've never built a set of RPM's I had always assumed you needed a working
version
everything before you could bundle it up into an RPM. Is this wrong? I'll try
reading
up on the RPM build process and see what I get.
    
    I'm near the end of my rope here and any advice would help

Thanks

Nick
nbuchholz@noao.edu
Day phone: (520) 318-8203
"Time is an illusion, Lunchtime doubly so" - Ford Prefect
Time is an illusion perpetrated by the manufacturers of space.

#2

Nick Buchholz wrote:

    I rebuilt python2.5 to use --with-unicode=UCS4.

If you replaced the system python with that then you may want to undo it, otherwise any other system RPMs you install that have Python extension modules will have a problem.

    I'm confused about the advice you gave in your last email. You suggested:

Have you tried making your own RPMs with rpmbuild as I suggested in the other mail? It really will take care of everything for you and you won't have to worry about any of this. You'll just have to install the RPMs it produces. They will include wxWidgets and wxPython and will be built for the Python on your system.

    I've never built a set of RPM's I had always assumed you needed a working
version everything before you could bundle it up into an RPM. Is this wrong?

Sort of. You do need to have any build dependencies installed first so the build can use them, but you do not need to have a built and working Foo to be able to make a Foo RPM. The rpm tool will do both the build and the bundle of the target package. The recipe that is followed to make this build, and that specifies how to bundle the files together, is the .spec file. Most of the time you should not need to edit this file at all, unless it was written for a different distro or something.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

#3

Nick Buchholz wrote:

    I rebuilt python2.5 to use --with-unicode=UCS4.

If you replaced the system python with that then you may want to undo it,
otherwise any other system RPMs you install that have Python extension modules
will have a problem.

I have tripped over that problem years ago when I installed python2.4 on a
system that used python2.2 for some system functions. I installed 2.5.2 next to
and without replacing the python link. the system functions use the old link
and to call python2.5 you use a script that sets everything properly.

    I'm confused about the advice you gave in your last email. You

suggested:

Have you tried making your own RPMs with rpmbuild as I suggested in the
other mail? It really will take care of everything for you and you
won't have to worry about any of this. You'll just have to install the
RPMs it produces. They will include wxWidgets and wxPython and will be
built for the Python on your system.

    I've never built a set of RPM's I had always assumed you needed a

working

version
everything before you could bundle it up into an RPM. Is this wrong?

Sort of. You do need to have any build dependencies installed first so the
build can use them, but you do not need to have a built and working Foo to be
able to make a Foo RPM. The rpm tool will do both the build and the bundle of
the target package. The recipe that is followed to make this build, and that
specifies how to bundle the files together, is the .spec file. Most of the
time you should not need to edit this file at all, unless it was written for a
different distro or something.

   OK, I have a copy of the RPM .spec file from the wxPython.org site and I've
modified it to build for python 2.5. I'll try it later today.

Nick
nbuchholz@noao.edu
Day phone: (520) 318-8203
"Time is an illusion, Lunchtime doubly so" - Ford Prefect
Time is an illusion perpetrated by the manufacturers of space.

···

On Mon, 13 Oct 2008 10:53:21 -0700 Robin Dunn <robin@alldunn.com> wrote: