On 10/30/2015 04:00 PM, Adriano dos Santos Fernandes wrote:
> On 30/10/2015 10:57, Adriano dos Santos Fernandes wrote:
>> On 30/10/2015 10:53, Dimitry Sibiryakov wrote:
>>> 30.10.2015 13:35, Adriano dos Santos Fernandes wrote:
>>>> I said that external plugins are not loaded without editing Firebird
>>>> supplied configuration files.
>>> Avalerion's CDC plugin is loaded perfectly well without editing
>>> plugins.conf.
>>>
>> What's the [Firebird] type of this plugin?
>>
> And, does it uses a .conf file through the API plugin?
>
> Of course, this is what I want, in addition to an easy-install approach,
> use the plugin's config within the Firebird plugin API.
>
Plugins can be loaded without changes in plugins.conf (the only one
plugin which needs it is UDR, the reason is plugin name does not match
executable module name). I suppose that after renaming libudr_engine.so
to libUDR.so parameter
Module = $(root)/plugins/udr_engine
will not be needed.
What about internal config values - they may be moved to
plugins/UDR.conf which will look as follows:
path = $(root)/plugins/udr
or even better
path = $(DIR_PLUGINS)/udr
I.e. editing of plugins.conf is normally not required for plugins - UDR
needs this (on my mind) due to historical reasons.
------------------------------------------------------------------------------
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
