[vlc-devel] Re: rfc: loadable modules from libvlc
Filippo Carone
filippo at carone.org
Mon Jan 8 20:41:45 CET 2007
Rémi Denis-Courmont ha scritto:
> Le lundi 8 janvier 2007 13:51, filippo at carone.org a écrit :
>> Hi everybody,
>> i'd like to know if it is ok for you to have functions in libvlc to
>> load a vlc plugins at runtime, ie after vlc bootstrap, to be released
>> with vlc version 0.9.0:
>
> Version 0.9.0 breaks the API and the ABI in almost every possible ways.
> If you (or anyone else) wants to modify something, the time is right :)
> That being said, adding new APIs does not normally break backward
> compatibility, so it does not matter.
Ok.
>> /*
>> * path The complete path to .so plugin file
>> */
>> void libvlc_core_load_module( const char* path, libvlc_exception_t
>> *p_e )
>> void libvlc_core_unload_module( char* plugin_name,
> ^^^^
> const char* ?
>> libvlc_exception_t *p_e )
yes, const char* of course.
> If I understand correctly, you want to load a file rather than a plugin
> name. Could be useful, but please avoid heavy duplication with
> module_Need et al (you may want to factorize some code).
Ok, I'll check for the right place where to put common functions.
> Are you sure you are not going to have some severe problems with the
> plugin cache, in particular if the plugin adds some configuration
> parameters?
That's what I'll discover. For sure, I won't touch the .dat file with to
store/read the plugin cache, since plugins loaded at runtime could be
kind of volatile.
Cheers,
Filippo
--
This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/
To unsubscribe, please read http://developers.videolan.org/lists.html
More information about the vlc-devel
mailing list