Ticket URL: <
http://trac.wxwidgets.org/ticket/14525#comment:3>
#14525: DirDialog.GetPath() doesn't return the user-selected path
--------------------------+-------------------------------------------------
Reporter: MichaelClerx | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: wxPython | Version: 2.8.12
Keywords: | Blockedby:
Patch: 0 | Blocking:
--------------------------+-------------------------------------------------
Comment(by MichaelClerx):
Ok, I've been trying but the library has a lot of dependencies so it's
taking some time to build.
Right now the build script is complaining about not being able to find
GStreamer, although it's definitely installed:
{{{
checking for GST... configure: WARNING: GStreamer 0.10 not available,
falling back to 0.8
checking for GST... configure: WARNING: GStreamer 0.8/0.10 not available.
configure: error: GStreamer not available
Error running configure
ERROR: failed building wxWidgets
Traceback (most recent call last):
File "./build-wxpython.py", line 378, in <module>
wxbuild.main(wxscript, build_options)
File "/home/michael/install/wxPython-src-2.9.4.0/build/tools/build-
wxwidgets.py", line 359, in main
"Error running configure")
File "/home/michael/install/wxPython-src-2.9.4.0/build/tools/build-
wxwidgets.py", line 74, in exitIfError
raise builder.BuildError(msg)
BuildError
[root@thinkpad wxPython]# yum list gstreamer*
Loaded plugins: langpacks, presto
Installed Packages
gstreamer.x86_64
0.10.36-1.fc17 @koji-
override-0/$releasever
gstreamer-devel.x86_64
0.10.36-1.fc17 @fedora
gstreamer-plugins-bad-free.x86_64
0.10.23-7.fc17 @updates
gstreamer-plugins-bad-nonfree.x86_64
0.10.22-3.fc17 @rpmfusion-
nonfree
gstreamer-plugins-base.x86_64
0.10.36-1.fc17 @koji-
override-0/$releasever
gstreamer-plugins-good.x86_64
0.10.31-4.fc17 @updates
gstreamer-plugins-ugly.x86_64
0.10.19-1.fc17 @rpmfusion-free
gstreamer-python.x86_64
0.10.19-3.fc17 @koji-
override-0/$releasever
gstreamer-rtsp.x86_64
0.10.8-2.fc17 @koji-
override-0/$releasever
gstreamer-tools.x86_64
}}}
Not to be rude, but if it works in 2.9, is your response going to be "Then
use 2.9"? Because I'd much rather find the origin of this behaviour in
2.8. I'm guessing it's not a problem in wxPython or even wxWidget (since
both versions I have installed seem to have been built sometime in
January, and this would have affected quite a lot of users since then),
but I don't have the know-how to dig into the underlying components
myself.
--
Ticket URL: <
http://trac.wxwidgets.org/ticket/14525#comment:3>