Incorrect architecture and configuration when calling “tizen build-app” (Tizen CLI) to build hybrid wearable app

Incorrect architecture and configuration when calling “tizen build-app” (Tizen CLI) to build hybrid wearable app

BY 22 Sep 2018 SDK & IDE

I’m running the following command to build my Tizen 3.0 hybrid wearable app (compiler: llvm-4.0, architecture: arm, platform: wearable-3.0):

tizen build-app -m "name:m1,compiler:llvm-4.0,rootstraps:[name:NativeService,platform:wearable-3.0,arch:arm],configs:[Release]" -b "name:b1,targets:[WebApp,NativeService],methods:[m1]" -p "name:MyPkg,targets:[b1]" -s MyProfile

 

The console output shows that the native app is built targeting i386 (not arm) architecture, and with Debug configuration (not Release):

package : MyPkg
package type : hybrid
project : %WebAppPath%
project : %NativeServicePath%
Wearable-3.0, i386
=== ====== ===
[PLATFORM] Wearable-3.0
[ARCHITECTURE] i386   <=======incorrect
[COMPILER] LLVM-4.0
[CONFIGURATION] Debug   <======= incorrect

 

If I remove the “rootstraps” parameter, then the app is built in Release configuration (good), but the app still targets i386 instead of arm (bad).

What is the correct CLI syntax for ensuring that my app is built targeting “arm” architecture, and only in Release mode?

Written by