Hi Radhika,

*For applications to use my plugin I will also have to make changes in
the libslp-tapi and tel-plugin-dbus_tapi to expose my functionality.*
It isn't clear what is actually meant here when you say "For applications
to use my plugin".
If your Plug-in provides the functionalities relevant to Telephony then
there is NO change required to *libslp-tapi* OR *tel-plugin-dbus_tapi*.
Yes, you may need some changes if your Plug-in provides additional
Telephony functionalities apart from for those for which interfaces are
already provided.

*And also i was unable to find how the telephony daemon is started.*
*Is it in some init file?*
As per the *telephony-daemon *file in *resource/etc/rc.d/init.d* folder in *
telephony-daemon* Plug-in,
*if [ ! -e /opt/etc/.hib_capturing ]; then
/usr/bin/telephony-daemon &
fi*
(
https://review.tizen.org/git/?p=framework/telephony/telephony-daemon.git;a=blob_plain;f=resource/etc/rc.d/init.d/telephony-daemon;hb=HEAD
)

Which means it must be started during Tizen boot-up sequence.

Warm Regards,
Suresh

On Fri, Dec 28, 2012 at 1:15 PM, Radhika Praveen <[email protected]>wrote:

> Thank you Suresh. That was a great answer.
>
> I see the telephony daemon is loading all the plugins that is available in
> the path:"/usr/lib/telephony/plugins/".
>
> So my understanding is all the plugins will be loaded at the start of the
> telephony service.
> And if i want to write my own plugin, i have to make sure it is loaded by
> telephony daemon.
> For applications to use my plugin I will also have to make changes in
> the libslp-tapi and tel-plugin-dbus_tapi to expose my functionality.
> Is this correct?
>
> And also i was unable to find how the telephony daemon is started.
> Is it in some init file?
>
> Regards
> Radhika
>
>
>
>
>
> On Fri, Dec 28, 2012 at 12:46 PM, Suresh Kumar N. <[email protected]>wrote:
>
>> Hi Radhika,
>>
>> Good to know build is successful!
>>
>>
>> *So is this the final output of the telephony module?*
>> YES, successful build would result in 3-4 RPMs as mentioned by you. Every
>> folder/Plug-in would generate it's own RPM.
>> In most of the cases it is just 3 RPMs -
>> *libslp-tapi-0.6.14-1.armv7l.**rpm                      - A*ctual RPM
>> that needs to be installed
>> *libslp-tapi-debuginfo-0.6.14-**1.armv7l.rpm     - *RPM that contains
>> information for debugging
>> *libslp-tapi-debugsource-0.6.**14-1.armv7l.rpm - *RPM that contains
>> references to Source files useful while debugging
>>
>> *libslp-tapi-devel-0.6.14-1.armv7l.rpm*
>> The other RPM generated depends on whether there is different branch
>> present (development) and is included in mainstream build.
>>
>> Installation of *libslp-tapi-0.6.14-1.armv7l.**rpm *is sufficient to get
>> *libslp-tapi* functionality.
>>
>>
>> *If so every folder/plugin is considered as separate library?
>> *
>> Not necessarily as a library, but each folder/Plug-in would generate it's
>> corresponding RPM (shared object).
>>
>>
>> *Is the plugins loaded dynamically or all the plugins are loaded when
>> the telephony service is started?*
>>  All these RPMs ( each Plug-in's) when installed, installs it's
>> corresponding '*.so*' in "*/usr/lib/telephony/plugins/*" folder.
>> These .so's are loaded by Telephony Server during it's initialization.
>>
>>
>> *My confusion is whether all these rpm files belonging to the telephony
>> folder constitute the telephony service or a separate single .so or .dll is
>> created for telephony service?*
>> NO, there is NO separate .so OR .dll created for Telephony Service apart
>> from these RPMs. As mentioned earlier, we need to install these RPMs
>> individually.
>> There is a possibility of these RPMs getting clubbed with the mainstream
>> Tizen Platform binary such that these RPMs would become part of Platform
>> binary and installation of Platform would in turn install these RPMs
>> (manual installation is not needed).
>>
>> Warm Regards,
>> Suresh
>>
>> On Fri, Dec 28, 2012 at 12:22 PM, Radhika Praveen 
>> <[email protected]>wrote:
>>
>>> Hi All,
>>>
>>> I built the telephony module alone.
>>> It built successfully.
>>> I was checking the output.
>>> It is available in the form of rpm files.
>>> For every folder in the telephony module 3 or 4 rpm files have been
>>> built. Below is one example:
>>>
>>> Inside folder GBS-ROOT\local\repos\tizen\armv7l\RPMS
>>> libslp-tapi-0.6.14-1.armv7l.rpm
>>> libslp-tapi-debuginfo-0.6.14-1.armv7l.rpm
>>> libslp-tapi-debugsource-0.6.14-1.armv7l.rpm
>>> libslp-tapi-devel-0.6.14-1.armv7l.rpm
>>>
>>> So is this the final output of the telephony module?
>>> If so every folder/plugin is considered as separate library?
>>> Is the plugins loaded dynamically or all the plugins are loaded when the
>>> telephony service is started?
>>>
>>> My confusion is whether all these rpm files belonging to the telephony
>>> folder constitute the telephony service or a separate single .so or .dll is
>>> created for telephony service?
>>>
>>> Regards
>>> Radhika
>>>
>>> _______________________________________________
>>> General mailing list
>>> [email protected]
>>> https://lists.tizen.org/listinfo/general
>>>
>>>
>>
>
_______________________________________________
General mailing list
[email protected]
https://lists.tizen.org/listinfo/general

Reply via email to