Languages

Menu
Sites
Language
command-line builds, using Tizen Studio?

My project is set up to use Tizen Studio, but for testing and automated builds, I'd like to be able to build from the command line.  I'm currently using the "Export to CLI Project" command in Tizen Studio to create a command-line project that I then build with "tizen build-native", but this is not ideal, for a few reasons:

1) Any time a change is made in Tizen Studio, the developer has to remember to export the CLI build files again.

2) The command-line build files encode absolute paths, which is terrible for build scripts.  For example, I have some include paths and library paths in my Tizen Studio project that are relative to ${PROJ_PATH}, but when I export them, they become absolute paths (e.g. /Users/steve/...).  This means they won't work on anyone else's computer.

3) I have some shell scripts that are set up as post-build steps in Tizen Studio (for example, to copy the final executable to another location), but it turns out that the environment variables are different when building on the command line.  For example, for an ARM build, $SDK_ARCH is "arm" in Tizen Studio, but it's not defined when doing a command-line build; instead there's $BUILD_ARCH, but the value isn't even the same ("armel" instead of "arm").

Is there any way to do a build from the command line, using Tizen Studio itself, in some kind of "headless" mode?

 

List

Responses

2 Replies
Steven Merel

Add to that list:

4) The compiler options are actually different: when building from Tizen Studio, it uses -mthumb, but not when building from the command line

5) While the compiler is called by full path, the archiver is not, which means that on my system, it used the Xcode ar, which produces an incompatible library.

 

 

Armaan-Ul- Islam

Hello Steven, I am sharing my experience with you.

  1. I created a project in Tizen studio and then exported to CLI once (for the first time). After that I have made some changes in code and could build it from CLI straight way. I didn’t need to export the project again. Which type of change you are talking about?
  2. I’ve also faced this absolute path issue and find it annoying.
  3. Good observation. I was not aware that environment variables have different names in GUI and CLI. “Headless” mode would be convenient.
  4. I didn’t know compiler options are actually different while building from the command line.

 

I hope Linux foundation would follow up the discussion and take input for further releases. However, my suggestion is to mail the Tizen dev community (application-dev@lists.tizen.org) to get a better understanding. If you find something out, please share in this forum.