It must be noted that an application cannot link against both APS and VAS. We verified that on 5th edition, an APS compiled application, simply does not start. It's required to "isolate" into a separate dll the audio interface in order to be able to have in one single executable all APS, VAS1, VAS2 support. This could be an improvement path for PJSIP in order to let S60 developers to link into one single application a VoIP client that support all the Nokia audio frameworks. In the meantime different executable or a very fat installer are required. Fabio On 19/03/10 10.59, Nanang Izzuddin wrote: > Hi Jerry, > > FYI, VAS is not available on 3rd ed plain/MR, so I am not sure if 3rd > ed and 5th ed devices can share same binary. Moreover, the 3rd ed, by > default uses VAS v1.0 while 5th ed uses VAS v2.0, so some effort will > be needed to apply VAS v2.0 on the 3rd ed devices. > > An alternative perhaps, as I haven't tried or digged deeper, it seems > that we can put platform or device check in the package config .pkg, > so we may be able to combine the binaries into single installer, and > specify what files to be installed depends on device platform type. > However, the installer .sis/.sisx size will get bloated. > > BR, > nanang > > > On Tue, Mar 2, 2010 at 11:45 AM, Jerry Monteiro > <jerrym at matrixconsultants.com.au> wrote: > >> Hi all >> >> Was wondering if anybody has managed to build for APS-Direct and VAS-Direct >> at the same time so that devices on 3rd ed and 5th ed can use the same >> binary? >> >> If you could share your code or provide guidance on how to achieve this, its >> very much appreciated. >> >> >> >> Regards >> >> >> >> Jerry >> >> >> >> _______________________________________________ >> 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 >
