SDK Problem: Kit configuration

Question

0

SDK Problem: Kit configuration

sdk

asked 2019-04-05 00:41:16 +0300

bomo
2292 ●43 ●60 ●61

updated 2019-04-05 00:41:29 +0300

I am trying (for the first time) to build a project using sailfish SDK (I am using SDK 2.0)

When trying to build a project, I get the following error

23:31:16: Running steps for project test...
23:31:16: Start Build Engine: The "Sailfish OS Build Engine" virtual machine is already running. Nothing to do.
23:31:16: Starting: "/home/xx/.config/SailfishOS-SDK/mer-sdk-tools/Sailfish OS Build Engine/SailfishOS-3.0.2.8-armv7hl/qmake" /home/xx/build/harbour-test/test.pro -spec linux-g++ CONFIG+=debug CONFIG+=qml_debug
bash: /home/src1/: is a directory
23:31:16: The process "/home/xx/.config/SailfishOS-SDK/mer-sdk-tools/Sailfish OS Build Engine/SailfishOS-3.0.2.8-armv7hl/qmake" exited with code 126.
Error while building/deploying project test (kit: SailfishOS-3.0.2.8-armv7hl (in Sailfish OS Build Engine))
The kit SailfishOS-3.0.2.8-armv7hl (in Sailfish OS Build Engine) has configuration issues which might be the root cause for this problem.
When executing step "qmake"
23:31:16: Elapsed time: 00:00.

To check the possible root for the problem, I checked the kit configuration which shows: image description

I am confused because it says that I cannot use the ARM toolchain on the build engine. I thought the build engine has/uses a SFOS emulator.

How to fix the kit configuration to build/debug using ARM architecture using the build engine/VM?

edit retag flag offensive close delete

Comments

The error in Kit configuration is unrelated to your build error - please edit your question and submit that part as a separate question.

Regarding the build error, 1) what is your SDK installation path? (default is ~/SailfishOS), 2) what is your value of Alt source folder in Options > Sailfish OS > Build Engine?

martyone ( 2019-04-05 08:09:50 +0300 )edit

@martyone thanks so much for your reply. I did not know how to verify the SDK install path, but I did not modify it. Within ~/SailfishOS is for example the SDKMaintenanceTool and the bin folder etc. The Alt source folder was ~/sfos_projects I changed it to ~/and now get a slightly different compile error: 09:14:59: Running steps for project LiveTrack... 09:14:59: Start Build Engine: The "Sailfish OS Build Engine" virtual machine is already running. Nothing to do. 09:14:59: Starting: "/home/xx/.config/SailfishOS-SDK/mer-sdk-tools/Sailfish OS Build Engine/SailfishOS-3.0.2.8-armv7hl/qmake" /home/xx/build/harbour-LiveTrack/LiveTrack.pro -spec linux-g++ CONFIG+=debug CONFIG+=qml_debug bash: /home/src1/: is a directory 09:14:59: The process "/home/xx/.config/SailfishOS-SDK/mer-sdk-tools/Sailfish OS Build Engine/SailfishOS-3.0.2.8-armv7hl/qmake" exited with code 126. Error while building/deploying project LiveTrack (kit: SailfishOS-3.0.2.8-armv7hl (in Sailfish OS Build Engine)) The kit SailfishOS-3.0.2.8-armv7hl (in Sailfish OS Build Engine) has configuration issues which might be the root cause for this problem. When executing step "qmake" 09:14:59: Elapsed time: 00:00.

The project I am trying to build is located in ~/build/harbour-LiveTrackand its source code is provided here https://github.com/jaykijay/harbour-LiveTrack/

bomo ( 2019-04-05 10:15:38 +0300 )edit

@bomo Please edit your ~/SailfishOS/mersdk/ssh/mersdk/authorized_keys, prepend command="/bin/bash -c 'set -x; eval \"$SSH_ORIGINAL_COMMAND\"'" to the only line (ensure the editor does not wrap the line, notice the space at the end). Then try to build and paste the build output up to the bash: /home/src1/: is a directory error.

martyone ( 2019-04-10 08:26:42 +0300 )edit

@martyone after switching to i486-kit it suddenly works. Not sure if it solely due to switchitng the kit or some other settings I touched. Thanks for your help!

bomo ( 2019-04-11 10:19:04 +0300 )edit

@bomo This didn't fix your issue - you are still not able to target ARM devices. I can't really help you without the debug output I asked for in my previous comment.

martyone ( 2019-04-12 07:48:07 +0300 )edit

The error in Kit configuration is unrelated to your build error - please edit your question and submit that part as a separate question.
Regarding the build error, 1) what is your SDK installation path? (default is ~/SailfishOS), 2) what is your value of Alt source folder in Options > Sailfish OS > Build Engine?
martyone ( 2019-04-05 08:09:50 +0300 )edit
@martyone thanks so much for your reply. I did not know how to verify the SDK install path, but I did not modify it. Within ~/SailfishOS is for example the SDKMaintenanceTool and the bin folder etc. The Alt source folder was ~/sfos_projects I changed it to ~/and now get a slightly different compile error: 09:14:59: Running steps for project LiveTrack... 09:14:59: Start Build Engine: The "Sailfish OS Build Engine" virtual machine is already running. Nothing to do. 09:14:59: Starting: "/home/xx/.config/SailfishOS-SDK/mer-sdk-tools/Sailfish OS Build Engine/SailfishOS-3.0.2.8-armv7hl/qmake" /home/xx/build/harbour-LiveTrack/LiveTrack.pro -spec linux-g++ CONFIG+=debug CONFIG+=qml_debug bash: /home/src1/: is a directory 09:14:59: The process "/home/xx/.config/SailfishOS-SDK/mer-sdk-tools/Sailfish OS Build Engine/SailfishOS-3.0.2.8-armv7hl/qmake" exited with code 126. Error while building/deploying project LiveTrack (kit: SailfishOS-3.0.2.8-armv7hl (in Sailfish OS Build Engine)) The kit SailfishOS-3.0.2.8-armv7hl (in Sailfish OS Build Engine) has configuration issues which might be the root cause for this problem. When executing step "qmake" 09:14:59: Elapsed time: 00:00.
The project I am trying to build is located in ~/build/harbour-LiveTrackand its source code is provided here https://github.com/jaykijay/harbour-LiveTrack/
bomo ( 2019-04-05 10:15:38 +0300 )edit
@bomo Please edit your ~/SailfishOS/mersdk/ssh/mersdk/authorized_keys, prepend command="/bin/bash -c 'set -x; eval \"$SSH_ORIGINAL_COMMAND\"'" to the only line (ensure the editor does not wrap the line, notice the space at the end). Then try to build and paste the build output up to the bash: /home/src1/: is a directory error.
martyone ( 2019-04-10 08:26:42 +0300 )edit
@martyone after switching to i486-kit it suddenly works. Not sure if it solely due to switchitng the kit or some other settings I touched. Thanks for your help!
bomo ( 2019-04-11 10:19:04 +0300 )edit
@bomo This didn't fix your issue - you are still not able to target ARM devices. I can't really help you without the debug output I asked for in my previous comment.
martyone ( 2019-04-12 07:48:07 +0300 )edit

Answer 1

0

answered 2019-04-10 00:04:07 +0300

hsjpekka
613 ●6 ●25 ●28

Emulator does not run programs compiled using armv7hl-kit, but those compiled using i486-kit. So you need i486-kit for testing the app in your computer, and armv7hl-kit for making an app to run in your phone.

If you compile using i486-kit, debug-build, and deploy as rpm-package, does the emulator run and open your app?

edit flag offensive delete publish link

Comments

As commented under the question, this is unrelated to the build error.

martyone ( 2019-04-10 07:38:29 +0300 )edit

Thanks! I did not know that! Now the build process works and the emulator starts. How to later obtain armv7 RPMs if I can't crosscompile them? Is it required to build it on the phone then?

bomo ( 2019-04-11 10:17:57 +0300 )edit

ARM RPMs can be built using the ARM kit.

martyone ( 2019-04-12 07:44:50 +0300 )edit

You can compile armv7 rpms as martyone wrote, but you can't run arm.rpms in your pc.

I use release-build to get a running version, and qt creator places it in folder build-APP_NAME-SailfishOS_3_0_1_11_armv7hl_in_Sailfish_OS_Build_Engine-Release/RPMS/ or similar.

Copy the APP_NAME.armv7hl.rpm in your phone, and install using FileBrowser, for example.

hsjpekka ( 2019-04-13 11:47:00 +0300 )edit

SDK Problem: Kit configuration

Comments

1 Answer

Comments

Question tools

Stats

Related questions

SDK Problem: Kit configuration

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions