I installed wxPython on Linux using the GTK2 and Unicode options.
I compiled everything from the sources following the instructions
in the README.1st.txt file of the wxPythonSrc distribution; i.p.
I used the following to configure wxGTK:
The result was that wxPython crashed very often (segfaults); i.p.
right-clicking in a TextCtrl widget caused wxPython to crash (e.g.
in demo.py, but also in my own applications).
I deleted wxPython and installed it without the GTK2 and Unicode
options and everything was OK (but ugly; moreover, I need Unicode).
So I gave the GTK2 and Unicode options a second chance; I did the
same as before, only changing the above configuration as follows:
../configure --with-gtk \ # did not use this option
--prefix=$WXPREF \
--enable-rpath=$WXPREF/lib \
--with-opengl \
--enable-geometry \
--enable-optimise \
--enable-debug_flag \ # did not use this option
--with-libjpeg=builtin \ # did not use this option
--with-libpng=builtin \ # did not use this option
--with-libtiff=builtin \ # did not use this option
--with-zlib=builtin \ # did not use this option
--enable-gtk2 \
--enable-unicode
The result: no more crashes; right clicking in a TextCtrl shows
a popup-menu, everything seems to be fine!
But: I do not understand why the second way of compiling wxPython
works whereas the first leads to the problems described above!?
Any hints?
My system: Fedora Core 1 Linux, Python 2.3.2 (compiled from source),
wxPython 2.4.2.4 (using wxPythonSrc-2.4.2.4.tar.gz), GTK+ 2.2.4
Juft FYI, we're using wxPython 2.4.1.2 on Python 2.3.1 on RH 8 compiled
for GTK2 but without Unicode. Things run fine in general and we haven't
seen any crashes with the demos, so far.
But there are spurious seg faults in GTK. For now, we try to work around
those by rearranging our code. Not great, but workable.
/Jean Brouwers
Logan wrote:
···
I installed wxPython on Linux using the GTK2 and Unicode options.
I compiled everything from the sources following the instructions
in the README.1st.txt file of the wxPythonSrc distribution; i.p.
I used the following to configure wxGTK:
The result was that wxPython crashed very often (segfaults); i.p.
right-clicking in a TextCtrl widget caused wxPython to crash (e.g.
in demo.py, but also in my own applications).
I deleted wxPython and installed it without the GTK2 and Unicode
options and everything was OK (but ugly; moreover, I need Unicode).
So I gave the GTK2 and Unicode options a second chance; I did the
same as before, only changing the above configuration as follows:
../configure --with-gtk \ # did not use this option
--prefix=$WXPREF \
--enable-rpath=$WXPREF/lib \
--with-opengl \
--enable-geometry \
--enable-optimise \
--enable-debug_flag \ # did not use this option
--with-libjpeg=builtin \ # did not use this option
--with-libpng=builtin \ # did not use this option
--with-libtiff=builtin \ # did not use this option
--with-zlib=builtin \ # did not use this option
--enable-gtk2 \
--enable-unicode
The result: no more crashes; right clicking in a TextCtrl shows
a popup-menu, everything seems to be fine!
But: I do not understand why the second way of compiling wxPython
works whereas the first leads to the problems described above!?
Any hints?
My system: Fedora Core 1 Linux, Python 2.3.2 (compiled from source),
wxPython 2.4.2.4 (using wxPythonSrc-2.4.2.4.tar.gz), GTK+ 2.2.4
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org
--with-libjpeg=builtin \ # did not use this option
--with-libpng=builtin \ # did not use this option
--with-libtiff=builtin \ # did not use this option
--with-zlib=builtin \ # did not use this option
--enable-gtk2 \
--enable-unicode
The result: no more crashes; right clicking in a TextCtrl shows
a popup-menu, everything seems to be fine!
But: I do not understand why the second way of compiling wxPython
works whereas the first leads to the problems described above!?
It's possible that there is a version clash with the libpng builtin to the wxGTK lib and one that is used with your current GTK theme or some other shared lib that is loaded.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!