Problem with CIQ Development with OpenSuse linux (Tumbleweed)

I was wondering whether starting the IQ simulator would be faster on Linux; it might be nice to develop on a Linux PC. So I decided to install the SDK and Eclipse. I had to solve 2 dependencies on my fresh Opense setup for the simulator to work, but that wasn't a problem. I can start the simulator from the command line and from the Eclipse menu. Also I can make a new IQ-project, like a datafield.

However, starting the simulator from the Run configurations gives a build error, with an imported datafield and with a new one:
======================================================
BUILD: /usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/bin/java -Dfile.encoding=UTF-8 -Dapple.awt.UIElement=true -jar /home/joop/connectiq-sdk/connectiq-sdk-lin-2.4.2/bin/monkeybrains.jar -o /run/media/joop/E6781546781516C1/Users/Joop/eclipse-workspace/Powerdashboard for Stryd plus/bin/Powerdashboard for Stryd plus.prg -w -y /home/joop/developer_key -d fenix5_sim -s 2.3.0 -f /run/media/joop/E6781546781516C1/Users/Joop/eclipse-workspace/Powerdashboard for Stryd plus/monkey.jungle
BUILD: Complete
Aborting launch due to failed build.
======================================================
BUILD: /usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/bin/java -Dfile.encoding=UTF-8 -Dapple.awt.UIElement=true -jar /home/joop/connectiq-sdk/connectiq-sdk-lin-2.4.2/bin/monkeybrains.jar -o /home/joop/eclipse-workspace/Test/bin/Test.prg -w -y /home/joop/developer_key -d fenix3_sim -s 1.3.0 -f /home/joop/eclipse-workspace/Test/monkey.jungle
BUILD: Complete
Aborting launch due to failed build.

"Export wizard" and "Creating for device" have no output as well....

Is there some way to debug this further?

sis651 over 7 years ago

I have SDK 2.4.1 on Kubuntu 17.10 and it works fine...

peterdedecker over 7 years ago

I see you use spaces in your project names. While it's allowed i've stopped using them as it caused issues in the past. So try to rename the project without spaces

for the 2nd project maybe try all lowercase

GHG23 over 7 years ago

Thnx, I will try that. Upper- and lowercase are handled differently by Windows and Linux, so that could be it as well. However, if it's one of those causes, it makes development a bit less atractive. ;)

asandweech over 7 years ago

Well, projects with names and paths containing a mix of spaces, upper, and lowercase all seem to work fine for me in mint and slackware, using openJDK 1.8.0_151.

Since it says build complete, does a prg get generated? If it does, are you able to run that prg manually using monkeydo? If monkeydo on linux fails, does that same prg run on a device, or in a windows sim? If a PRG is not generated, what happens when you try to compile manually?

GHG23 over 7 years ago

Manual compiling showed me what was wrong: eclipse was looking for the java binary in the wrong place. I had to make a symlink from
/usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/jre/bin to /usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/bin
Thanks!

What I wanted to check out, was whether the simulator would start quicker under Linux (OpenSuse Tumbleweed) than under Windows (10); I would then develop under LInux. However, it's even a bit slower, as far as I can see. I am using a Ryzen 1600 PC with 16Gb RAM and a SSD for storage.

asandweech over 7 years ago

whether the simulator would start quicker under Linux (OpenSuse Tumbleweed) than under Windows (10); I would then develop under LInux. However, it's even a bit slower, as far as I can see.

Are you starting and restarting the simulator enough that this is an issue? Or are you referring to startup time as being the transfer time for a PRG from eclipse to the sim? My normal workflow is to start the sim once at the same time as eclipse and leave it up. The transfer time to the sim isn't enough to bother me, but you could try the oracle released jdk. I don't know if that would make any difference though, especially if you are already using OpenJDK on windows anyway.

I am using a Ryzen 1600 PC with 16GB RAM and a SSD for storage.

Same setup as my mint build. Maybe you just need to load eclipse and the sim into a ramdisk on boot, heh, or switch to a few NVMe in raid 0. That oughta solve it.

GHG23 over 7 years ago

It was about the transfer. RAM-disk would be a possibility!

Former Member over 7 years ago

I don't think the slow time to get an app running on the simulator is due to Eclipse -- I don't use Eclipse, and I have the same problem.