[datatype-dev] hxclient_2_1_0_cayennes s60 v3 build state
Darrin.Mann at nokia.com Darrin.Mann at nokia.comThe Symbian player has not been ported to S60 3.0. Darrin ________________________________ From: datatype-dev-bounces at helixcommunity.org [mailto:datatype-dev-bounces at helixcommunity.org] Sent: Friday, November 10, 2006 1:28 PM To: richard.poirier at voiceage.com; angelo.degiorgio at voiceage.com; datatype-dev at helixcommunity.org Subject: RE: [datatype-dev] hxclient_2_1_0_cayennes s60 v3 build state ________________________________ From: ext Richard Poirier [mailto:richard.poirier at voiceage.com] Sent: Thursday, November 09, 2006 4:17 PM To: Gupta Ashish.As (Nokia-TP-MSW/Dallas); Angelo DeGiorgio; datatype-dev at helixcommunity.org Subject: RE: [datatype-dev] hxclient_2_1_0_cayennes s60 v3 build state Hi Ashish, Yes, I need a full-blown client with UI (and the ability to stream or play back local content) running on the N91...among other phones in the same generation. The ultimate goal is to play content with a new audio codec that I will integrate into the client. <Ashish>For the full blown client with UI, helix-client-s60-basic.pf/symbianplayer would be a better profile and target. I've tried a few targets/profile combos with varying numbers of failed modules. For the 3rd edition SDKs, it's probably clearer to mention what's in my local Symbian folder: 9.1/S60_3rd 9.1/S60_3rd_b 9.2/S60_3rd_FP1 [plus some 2nd edition SDKs]. I am usually defining SetSDKPath("SYMBIAN91SDK", "C:\\Symbian\\9.1\\S60_3rd"). I do manage to get more modules to build by copying missing headers I can't locate from older SDKs, such as 2nd edition. But some headers, like those mentioned in my last message, I could not locate. Using target/profile : symbianplay/helix-client-s60-mmf-mdf-arm gives me 13 of 87 failed modules with the headers mentioned in my previous message. (I should mention also that I get a "Failed to find path to SDK named 'faad2_include'." but am ignoring this for the moment as I don't consider it related to my problems) I have another question, related to the RealPlayer integrated in Symbian. Let's say I want to add a new audio codec into RealPlayer, rather than building and installing the entire helix player on the handset. Can I take the relevant dlls I've built with helix and "drag" them the Symbian Realplayer to get the new functionality? Seems like asking for trouble, but I have had some success with this with the PC version of RealPlayer. <Ashish> N91 doesn't contain helix so dropping a helix built codec dll as it is will not work. Entire symbianplayer needs to be installed to get the desired functionality. "Drag" and "drop" would work on the codewarrior but on the hardware I would install all the signed binaries including the codec dll of interest. Symbian builds can generate sis file that can be signed and installed. Angelo ________________________________ From: Ashish.As.Gupta at nokia.com [mailto:Ashish.As.Gupta at nokia.com] Sent: 9 novembre 2006 13:04 To: Richard Poirier; Angelo DeGiorgio; datatype-dev at helixcommunity.org Subject: RE: [datatype-dev] hxclient_2_1_0_cayennes s60 v3 build state Hi Agelo, It seems that your SDK doesn't have the desired headers. Which SDK are you using ? This branch/profile/target may not work for the environment you are trying. I haven't built other profile target options but you might be able to get away with this build problem with the profile helix-client-s60-mmf-basic.pf and target symbianMmf. Do you need a controller or UI Player? This would generate Helix MMF controller. I don't think it would work as it is on N91 because N91 already has another MMF controller with some shared UIDs as the Helix MMF Controller. If you need a UI player then symbianplayer would be better target. Ashish ________________________________ From: ext Richard Poirier [mailto:richard.poirier at voiceage.com] Sent: Thursday, November 09, 2006 9:04 AM To: Gupta Ashish.As (Nokia-TP-MSW/Dallas); Angelo DeGiorgio; datatype-dev at helixcommunity.org Subject: RE: [datatype-dev] hxclient_2_1_0_cayennes s60 v3 build state (on behalf of Angelo... seems like Angelo's e-mail are being hold back by the moderator or something so I'll try using my account) --------------------------------- Hi Ashish, Ok, using profile helix-client-s60-mmf-mdf-arm gives me 15 of 76 modules failed, which is progress... All the errors seem to be related to not finding the following headers (none of which were checked out by CVS): mmf/devvideo/devvideoconstants.h etelpckt.h RtpHeader.h Would the solution be to include them manually, and if so, where do I find them? Thanks, Angelo ________________________________ From: datatype-dev-bounces at helixcommunity.org [mailto:datatype-dev-bounces at helixcommunity.org] On Behalf Of Ashish.As.Gupta at nokia.com Sent: 7 novembre 2006 11:45 To: Angelo DeGiorgio; datatype-dev at helixcommunity.org Subject: RE: [datatype-dev] hxclient_2_1_0_cayennes s60 v3 build state HI Angelo, SYSTEM_ID is symbian-91-armv5 for hardware and symbian-91-winscw-emulator for codewarrior. Branch and profile settings are [0] Set BIF branch (hxclient_2_1_0_cayennes) [1] Set Target(s) (symbianMmf_rel) [2] helix-client-s60-mmf-basic (preferred for public SDKs) OR [2] helix-client-s60-mmf-mdf-arm Ashish ________________________________ From: datatype-dev-bounces at helixcommunity.org [mailto:datatype-dev-bounces at helixcommunity.org] On Behalf Of ext Angelo DeGiorgio Sent: Monday, November 06, 2006 2:14 PM To: datatype-dev at helixcommunity.org Cc: Angelo DeGiorgio Subject: [datatype-dev] hxclient_2_1_0_cayennes s60 v3 build state Hi, I would like to get the helix client up and running on an s60 v3 phone (Nokia N91). I'm thinking the best branch - or maybe the only branch - for this is the hxclient_2_1_0_cayennes. Can anyone tell me what settings are currently working in terms of system-ID / profiles, and what is the overall state of this branch (I know...it's beta)? Trying to build always ends with multiple failed modules and a Ribosome bug error as follows...: You have found a Ribosome bug. ----------------------------------------------------------- --- Python Traceback -------------------------------------- ------------------------------------ Traceback (most recent call last): File "C:\helixsymbian\build\bin\launcher.py", line 117, in __runTool tool.run() File "C:\helixsymbian\build\lib\build_exe.py", line 896, in run ShellToolApp().main() File "C:\helixsymbian\build\lib\build_exe.py", line 470, in main apply(self.menu[i][1], self.menu[i][2:]) File "C:\helixsymbian\build\lib\build_exe.py", line 584, in Build self.build(self.flags) File "C:\helixsymbian\build\lib\build_exe.py", line 492, in build invoke_buildsystem(arg_list) File "C:\helixsymbian\build\lib\build_exe.py", line 111, in invoke_buildsystem app = buildapp.RunBuild(arg_list) File "C:\helixsymbian\build\lib\buildapp.py", line 102, in RunBuild app.main() File "C:\helixsymbian\build\lib\buildapp.py", line 196, in main self.run() File "C:\helixsymbian\build\lib\buildapp.py", line 400, in run self.sign() File "C:\helixsymbian\build\lib\buildapp.py", line 1307, in sign raise err.error, e Build System Error: Cannot list directory="release". ----------------------------------------------------------- Traceback (most recent call last): File "C:\helixsymbian\build\bin\build.py", line 67, in ? tool.run() File "C:\helixsymbian\build\bin\launcher.py", line 97, in run self.__runTool() File "C:\helixsymbian\build\bin\launcher.py", line 117, in __runTool tool.run() File "C:\helixsymbian\build\lib\build_exe.py", line 896, in run ShellToolApp().main() File "C:\helixsymbian\build\lib\build_exe.py", line 470, in main apply(self.menu[i][1], self.menu[i][2:]) File "C:\helixsymbian\build\lib\build_exe.py", line 584, in Build self.build(self.flags) File "C:\helixsymbian\build\lib\build_exe.py", line 492, in build invoke_buildsystem(arg_list) File "C:\helixsymbian\build\lib\build_exe.py", line 111, in invoke_buildsystem app = buildapp.RunBuild(arg_list) File "C:\helixsymbian\build\lib\buildapp.py", line 102, in RunBuild app.main() File "C:\helixsymbian\build\lib\buildapp.py", line 196, in main self.run() File "C:\helixsymbian\build\lib\buildapp.py", line 400, in run self.sign() File "C:\helixsymbian\build\lib\buildapp.py", line 1307, in sign raise err.error, e Build System Error: Cannot list directory="release". ------------------------------------------------------------------------ ---- Your help much appreciated, Angelo VoiceAge -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.helixcommunity.org/pipermail/datatype-dev/attachments/20061110/436efc7d/attachment-0001.html