Generic Application for Symbian Platform - How to reduce the cost

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks Srivatsan,

I think this is the perfect solution which must solve my problem. Now I have
to test only a thing that the MR CReated SIS File  works on all the S60 FP1,
FP2 and S60v5 devices then we can make a package accordingly.


Regards:
Ravi



On Thu, Oct 15, 2009 at 1:36 PM, Srivatsan Deenadayalan <
srivatsan at ongobiz.com> wrote:

>  Forgot to add,
>
> Refer this link :
> http://wiki.forum.nokia.com/index.php/Advanced_Package_File_Options and
> concentrate on *Installing Platform Specific Files* section.
>
> Regards,
> Srivatsan D
>
>
> Srivatsan Deenadayalan wrote:
>
> Hi,
>
> In pkg file you can check the device type and install the corresponding APS
> sis. The technique of including a SIS in pkg file is called as Embedded SIS.
>
> You can also try giving search "Advance Package File in Symbian" in google
> and can find the below suggestion.
>
> This is how i use in my application, based on the device type the APS sis
> files are installed. So a single sis file will be generated and used across
> all symbian platforms.
>
>
> PKG File
> ****************************************************
>
> IF exists("Z:\system\install\Series60v3.2.sis")
>
>     @"APS_MR.sisx",(0x200081CD)
>
> ELSEIF exists("Z:\system\install\Series60v3.1.sis")
>
>     @"APS_FP1.sisx",(0x200081CD)
>
> ELSEIF exists("Z:\system\install\Series60v3.0.sis")
>
>     @"APS_FP2.sisx",(0x200081CD)
>
> ENDIF
>
> ****************************************************
>
> Hope this helps...
>
> Thanks,
> Srivatsan D
>
>
>
> varun pratapsingh wrote:
>
> Thanks Mukesh,
>
> But again if we consider you b) point that is
>
> Regarding APS, While Deploying the SIS File , have different versions of
> APS Server File. like Example.
>
>    -      MR CReated SIS File  +  APS MR SISX File
>    -      MR CReated SIS File  +  APS FP1 SISX File
>    -      MR CReated SIS File  +  APS FP2 SISX File
>
> we will again have the three SIS files for 3rd Edition and three SIS files
> for S60v5 as above. Then total 6 SIS files to be signed for the 3rd Edition
> and 5th edition. Again the purpose of saving the signing cost is not solved.
>
>
>  I think vishal is trying to say
>
>    - MR Created SIS File + APS MR SISX file
>
> will run on all S60v3 and S60v5 phones.
>
> Well clear vishal and please give me a application to test.
>
>
> Regards:
> Ravi
>
>
> On Wed, Oct 14, 2009 at 7:31 PM, Mukesh Srivastav <muki_champs at yahoo.com>wrote:
>
>>  Dear  Varun/Ravi,
>>
>> you are not trying to understand, what vishal is saying.  here is the
>> brief explanation.
>>
>> a. Compile your code only With MR SDK only and create only SIS File.
>>
>> b. Regarding APS, While Deploying the SIS File , have different versions
>> of APS Server File. like Example.
>>
>>
>>    -      MR CReated SIS File  +  APS MR SISX File
>>    -      MR CReated SIS File  +  APS FP1 SISX File
>>    -      MR CReated SIS File  +  APS FP2 SISX File
>>
>>
>> Cheers   :)
>> Mukesh.
>>
>>
>>  <http://www.geocities.com/muki_champs>
>>
>>
>>  ------------------------------
>> *From:* varun pratapsingh <varunps2003 at gmail.com>
>> *To:* pjsip list <pjsip at lists.pjsip.org>
>> *Sent:* Wed, October 14, 2009 3:18:30 PM
>> *Subject:* Re: [pjsip] Generic Application for Symbian Platform - How to
>> reduce the cost
>>
>> Hi Vishal
>>
>> Thanks again,
>>
>> but can you elaborate the process. See give me a link where I can download
>> all three S60v5 SDKs . See you must have selected the all 3 S60v5 SDKs and
>> all three S60v3 SDKs while building the sis file in the Carbide 2.0. Is this
>> that way or you just build it for anyone SDK from them and then it s working
>> on all of them. Please high light your procedure.
>>
>> Yes APS is another important consideration and then we will see the
>> APSServer versions compatibilty too but can we find other way yo generalise
>> the APSServer too fro both S60v5 and S60v3.
>>
>> And the last not but the least I think the APS support is not given on the
>> S60v5 devices by PJSIP so we will have to generalise the things from S60v3
>> FP1 to  S60v5 and that is through the VAS the generalising the VASServer is
>> much better.
>>
>> Hopes this discussion will be useful stuff for all the PJSIP community.
>>
>> Thanks and please I need more generalisation and comments.
>>
>>
>> Regards:
>> Ravi
>>
>> On Wed, Oct 14, 2009 at 2:51 PM, varun pratapsingh <varunps2003 at gmail.com
>> > wrote:
>>
>>> Thanks Vasyl,
>>>
>>> Can we build the sis file more generic like a single sis serving all the
>>> S60 5th Edition and S60 3rd Edition phones.
>>>
>>>
>>> Regards:
>>> Ravi
>>>
>>> On Wed, Oct 14, 2009 at 2:46 PM, Vasyl Strutynskyy <
>>> vasyl.strutynskyy at gmail.com> wrote:
>>>
>>>> Hi Ravi
>>>>
>>>> You can create only one installation file and hence sign only one hence
>>>> save your money :).
>>>>
>>>> Actually APS is supported by MR, FP1 and FP2 platforms. I think you will
>>>> build (create exe files) for each SDK and then pack these 3 exe file to one
>>>> sis.
>>>>
>>>> For details please go to forum Nokia:
>>>> http://discussion.forum.nokia.com/forum/search.php.
>>>>
>>>> Best Regards
>>>> *Vasyl
>>>>
>>>> 2009/10/13 varun pratapsingh <varunps2003 at gmail.com>
>>>>
>>>>>  Dear All,
>>>>>
>>>>> I have build the .sis file for the S60 3rd Edition FP1. So it is
>>>>> working well on all of the FP1 Devices, but as you know integration of  APS
>>>>> will require complete symbian signing. So for three SDK of the S60 3rd
>>>>> edition there will be three .sis files and three symbian signing. This is a
>>>>> very cost inclusive process.
>>>>>
>>>>> I am looking for a way so that a single application can run on three
>>>>> platforms that is FP1, MR and FP2 of S60 3rd Edition or more platforms is
>>>>> there any way.
>>>>>
>>>>> Thanks in advance......
>>>>>
>>>>>
>>>>> Regrads:
>>>>> Ravi
>>>>>
>>>>>  _______________________________________________
>>>>> Visit our blog: http://blog.pjsip.org
>>>>>
>>>>> pjsip mailing list
>>>>> pjsip at lists.pjsip.org
>>>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Visit our blog: http://blog.pjsip.org
>>>>
>>>> pjsip mailing list
>>>> pjsip at lists.pjsip.org
>>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>>>
>>>>
>>>
>>
>>
>  ------------------------------
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing listpjsip at lists.pjsip.orghttp://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20091015/f5833d26/attachment-0001.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux