Difference between revisions of "Autoloader for extra exeDSP plugins (B65x)"
| Line 1: | Line 1: | ||
| − | + | '''Plugin? What is this for ?''' | |
| + | |||
| + | Extra exeDSP plugin is a dynamically-loaded library file (*.so) that may be executed using "Game" menu of the Content Library. Normally, such plugin is brought to you together with "clmeta.dat" XML file that points to the main library file to be started ("loader.so", for example). There are many plugins already made by SamyGO community. (Almost) all of them require to be run from Content Library "Game" submenu. | ||
| + | |||
| + | '''The problem is...''' | ||
| + | |||
| + | You cannot execute such plugins using starting script. You even cannot run them using telnet shell. So, they cannot be started automatically. Even if you make an application that run any plugin, then exeDSP functions (symbols) would be unknown. These functions are used by plugins for accessing of hardware layer easily. | ||
| + | |||
| + | '''Why to autostart ?''' | ||
| + | |||
| + | Some plugins are intended to be run in the background. Unfortunately, you have to enter Content Library to execute them. This is confusing in some situations. Autostarting is useful for staying resident applications that are waiting for a specified signal to execute a piece of its code. Starting plugins automatically will save your remote control, your fingers and... your nerves. | ||
| + | |||
| + | '''Then how to autostart my plugin ? What should I do ?''' | ||
| + | |||
| − | |||
To be continued soon... | To be continued soon... | ||
| + | |||
| + | '''Under construction.''' | ||
Meanwhile, take a look at [http://forum.samygo.tv/viewtopic.php?f=5&t=594 this discussion]. | Meanwhile, take a look at [http://forum.samygo.tv/viewtopic.php?f=5&t=594 this discussion]. | ||
| − | [[User:Geo650|Geo650]] | + | --[[User:Geo650|Geo650]] 21:31, 3 May 2010 (UTC) |
Revision as of 21:31, 3 May 2010
Plugin? What is this for ?
Extra exeDSP plugin is a dynamically-loaded library file (*.so) that may be executed using "Game" menu of the Content Library. Normally, such plugin is brought to you together with "clmeta.dat" XML file that points to the main library file to be started ("loader.so", for example). There are many plugins already made by SamyGO community. (Almost) all of them require to be run from Content Library "Game" submenu.
The problem is...
You cannot execute such plugins using starting script. You even cannot run them using telnet shell. So, they cannot be started automatically. Even if you make an application that run any plugin, then exeDSP functions (symbols) would be unknown. These functions are used by plugins for accessing of hardware layer easily.
Why to autostart ?
Some plugins are intended to be run in the background. Unfortunately, you have to enter Content Library to execute them. This is confusing in some situations. Autostarting is useful for staying resident applications that are waiting for a specified signal to execute a piece of its code. Starting plugins automatically will save your remote control, your fingers and... your nerves.
Then how to autostart my plugin ? What should I do ?
To be continued soon...
Under construction.
Meanwhile, take a look at this discussion.
--Geo650 21:31, 3 May 2010 (UTC)
