[vlc-devel] Re: python binding compilation problem
kwangyul.seo at gmail.com
Thu May 3 17:54:45 CEST 2007
I did what you said.
The following is the stack trace. I compiled it again with the trunk
#0 0x7009e0d6 in mediacontrol_exception_init ()
#1 0x1000161d in VLC_AddTarget (i_object=268465184,
psz_target=0xc0ce10 "\001", ppsz_options=0x0, i_options=0,
i_mode=12635664, i_pos=13811384) at libvlc.c:314
#2 0x1e0d855b in _image_base__ ()
#3 0x1e1e7e18 in _image_base__ ()
(gdb) Cannot access memory at address 0x1c
I tried http://wiki.videolan.org/Python_bindings#Win32_initialization too,
but the same result came out.
2007/4/27, Olivier Aubert <olivier.aubert at liris.cnrs.fr>:
> > It compiles when I remove -lvlc-control from vlc-config and copy
> > libvlc.* into src/.libs.
> This comes from a bug introduced by the split of the VLC libs into
> libvlc and libvlc-control. vlc-config outputs the right command line
> options if libtool was enabled, but incorrect ones without libtool. A
> solution is to --enable-libtool, but I do not know its status on
> > After this, vlc crashed immediately. Is it reliable enough (is this
> > my mistake?) or still being tested?
> You should describe more precisely the crash, and give at last some
> error messages (possibly by invoking MediaControl with --verbose 2):
> mc=vlc.MediaControl('--verbose 2'.split())
> Did you have a look at
> http://wiki.videolan.org/Python_bindings#Win32_initialization ?
> This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/
> To unsubscribe, please read http://developers.videolan.org/lists.html
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vlc-devel