generate all the files needed to build vlc. You can then run configure.
Run ./configure --help for a description of the available options.
If you do not have the correct version of these tools, or if they are
simply not available for the operating system you plan to develop on,
generate all the files needed to build vlc. You can then run configure.
Run ./configure --help for a description of the available options.
If you do not have the correct version of these tools, or if they are
simply not available for the operating system you plan to develop on,
as a recent Linux distribution), run bootstrap, and then copy the whole
tree to your retarded OS.
as a recent Linux distribution), run bootstrap, and then copy the whole
tree to your retarded OS.
inside that directory. Do not forget to add a corresponding
Makefile line at the end of configure.ac for this new Modules.am file.
inside that directory. Do not forget to add a corresponding
Makefile line at the end of configure.ac for this new Modules.am file.
VLC_ADD_BUILTINS to configure.ac with your new module name as argument.
Look at other modules for guidelines on how to add build and linkage options.
After changing configure.ac you will always need to rerun bootstrap and
configure.
VLC_ADD_BUILTINS to configure.ac with your new module name as argument.
Look at other modules for guidelines on how to add build and linkage options.
After changing configure.ac you will always need to rerun bootstrap and
configure.
-VLC keeps a cache of its module (in ~/.vlc/cache on Linux), so you'll have to delete it. (or use vlc --reset-plugins-cache)
-Then use vlc -vvv --color --list to check that your plugin is seen by VLC.
+VLC keeps a cache of its modules (in ~/.cache/vlc/ on Linux), so you'll have to
+delete it (or use vlc --reset-plugins-cache). Then use vlc -vvv --color --list
+to check that your plugin is seen by VLC.