----------------------------------------------- Intel Corporation NV/SA Kings Square, Veldkant 31 2550 Kontich RPM (Bruxelles) 0415.497.718. Citibank, Brussels, account 570/1031255/09
From: Alejandro Piñeiro [mailto:[email protected]] Sent: Monday, November 03, 2014 5:56 PM To: [email protected] Cc: VanCutsem, Geoffroy Subject: Re: [Tizen General] Creating Tizen Native Project Error Hi, On 03/11/14 17:17, VanCutsem, Geoffroy wrote: From: General [mailto:[email protected]] On Behalf Of Alejandro Piñeiro Sent: Friday, October 24, 2014 7:22 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Tizen General] Creating Tizen Native Project Error On 23/10/14 17:35, VanCutsem, Geoffroy wrote: Hi, That link explains that the Tizen IDE has integration with GBS: https://wiki.tizen.org/wiki/Platform_Development_Using_IDE#GBS_Options_Setting And although seems to be really focused on tizen 2.X, it includes some references to Tizen 3.0. That seems to suggests that Tizen IDE/SDK should work there too. So, taking all this into account, is that wiki page correct, or as you suggest it is better to use GBS manually (meaning that the page is somewhat outdated)? [Geoffroy] This is a good question, I have seen that page a while ago but have never tried to actually use it. It would be good to get confirmation from the Tools team as to how mature/functional that solution is. All developers/contributors that I know use GBS and MIC at the command-line. Well, since my email, then some discussion happening on tizen-ivi, and this was said on one of those emails: "Although currently IVI SDK doesn't support native apps(I am not sure if IVI SDK also need to support native apps in future). It is a key issue for Tizen SDK(including mobile SDK, wearable SDK, or others)." [Geoffroy] This is referring to something slightly different, you have three types of apps you can develop for Tizen: Web apps, Native apps and Core apps. Web apps use the Tizen Web APIs, Native apps use the Tizen Native APIs (only available in Mobile) and Core Apps are applications which leverage the middleware components APIs, i.e. using oFono D-Bus API directly or the EFL APIs, etc. These Core APIs are obviously there but are not part of any compliance and there is no continuity guaranteed for those (i.e. oFono or EFL could be upgraded at any time and as a result the APIs could change at any time). The Tizen SDK reflects this split by providing an environment that allows you to develop a Web or Native (mobile-only) app or a Core app. The latter is what is referred to as PDK (Platform Development Kit). So the conclusions is that depends on the profile, and that the wiki page is somewhat outdated. Is the documentation also JIRA tracked? [Geoffroy] If this is a wiki page (hosted on wiki.tizen.org) then you can edit it yourself directly as long as you have a Tizen account (in fact, I would encourage you to). If the page is part of a non-editable area (such as source.tizen.org or others) then the best way is to file a JIRA ticket to get this updated. Full email: https://lists.tizen.org/pipermail/dev/2014-October/004758.html And now something somewhat offtopic, there is one thing that I miss from the tizen documentation. Although it properly and detailed explains how to create a new image based on the tizen repositories locally (using gbs), it is not clear how to create a new native application, compile and test it on a image, before event suggesting to integrate it on the Tizen machinery. Or am I wrong and there is a similar link around that I missed? [Geoffroy] There isn't such a wiki page that I'm aware of. The process to go through would be roughly the following: - Host your source code in a git repository. - Prepare the packaging info (aka your spec file) for it (for GBS): https://wiki.tizen.org/wiki/Packaging/Guidelines and put it under the 'packaging/' folder (in your source code. - Put your manifest file in 'packaging' too (see this wiki page for more info: https://wiki.tizen.org/wiki/Security/Application_installation_and_Manifest) - Build your code against Tizen using GBS: if successful this will generate an RPM file that you can then transfer and install in your Tizen image. Just note that with Yocto, the packaging information is different and comes in the form of a recipe that bitbake will use. That is a really good explanation. Thank you very much. And I think that it would be good to be included as part of the documentation (not sure exactly where). [Geoffroy] I'll find this a home somewhere on the wiki then, thanks! Thanks for your answer Best regards -- Alejandro Piñeiro ([email protected]<mailto:[email protected]>)
_______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
