I thought it might be useful to outline my experience attempting to actually get Tizen to build going by the documentation out of the website.
After some travails in just getting the IVI July 29, 3.0-M2-Jul to install, because raw dd and bmaptool with the --nomapoption did not seem to work correctly on my system, I was able to bring up a bootable Tizen image on my device. Unfortunately, the wiki instructions listed here: https://wiki.tizen.org/wiki/IVI/IVI_July_29,_3.0-M2-Jul ...said to use "wrt-launch" to see the demo, and this command was not on the system. I thought this might have simply been left off, but it actually turned out that the name of the executable is "wrt-launch*er*" with the "er" on the end, which one of my co-workers discovered searching around trying to find non-normal components. I edited the wiki page to properly reflect the actual command name. The wrt-launcher also fails to launch in -d debug mode, and there doesn't seem to be any explanation for it. Also, the wrt-install*er* doesn't appear to install packages correctly either. Issuing: wrt-installer -i test.wgt to install a small sample widget downloaded onto the box, gives me the following: appcore: appcore: setlocale() error ==================================== [Followed by a printout of the arguments used] (In case you're curious, test.wgt is just the Tizen piano-keyboard phone test app.) I don't have a workaround for this, but from googling, it appears to be a relatively common type of problem. I fully understand that something may need to be done to get it to work. Maybe editing TizenPolicy.xml or something. But the current error message is entirely unhelpful. The other issue I found was with trying to just get gbs to be functional at all. From what I can tell, the example could not possibly work. gbs clone --packaging-branch=tizen_2.1 tizen:pkgs/a/avsystem pkgs/a/avsystem It does not appear as if the trailing argument ever works. This was what I was able to get to work (or at least not immediately fail): gbs clone --packaging-branch=tizen tizen:apps/core/preloaded/app-selector But I'm not exactly sure about the setup from here on. It doesn't seem to preserve the source tree structure at all. I'm really not sure of my way forward. I was hoping that I could just clone the entire tree and poke around a bit, but trying to clone AllProjects.git (in the hopes that all the subprojects would come with it) resulted in a python script crashing inside gbs. -- Kind Regards Steven Maurer ------------------- Infotainment Engineer MSX on behalf of Jaguar Land Rover One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, Oregon, 97204 Email: [email protected] ------------------- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
