SDK on Windows Subsystem for Linux

While I might question the wisdom of using the Linux SDK under WSL, especially because of all the reports of issues with the Linux SDK, here's the link if you want to try:

https://developer.garmin.com/downloads/connect-iq/sdk-manager/connectiq-sdk-manager-linux.zip

You could do literally everything else with the WSL subsystem (like use git, run scripts / command line builds, use vi, etc.), and still use the CIQ Windows SDK. You can even open Windows VS Code from a WSL prompt, with the VS Code Remote WSL extension.

I happen to use the Windows CIQ SDK along with bash/gcc/etc. under WSL for certain automation / additional build steps.

I just think that Windows and Mac are always going to have better support from Garmin....

I totally agree with you on WSL and that's exactly what I do (git, scripts, vscode, ...). 

I want to use it on Linux because it's easier to use the command lines and use makefile/openssl without having to download and configure them for Windows. Plus, on linux I would be able to create a script that does everything for me when I start coding, and I don't know that much of windows cmd prompt...

Anyway, when I unzip the file and I do ./sdkmanager I get an error : ./sdkmanager: error while loading shared libraries: libwebkitgtk-1.0.so.0: cannot open shared object file: No such file or directory

Do you know how to deal with it ?

See forums.garmin.com/.../1187028

I tried what I found with your link but when I do :

deb cz.archive.ubuntu.com/ubuntu bionic main universe

sudo apt-get update
sudo apt-get install libwebkitgtk-1.0-0

I get an error with the update : E: Malformed entry 51 in list file /etc/apt/sources.list (URI parse)
E: The list of sources could not be read.

I hope I can do it on WSL because I don't know if it's possible to use a GUI on an headless version of linux

You don't want to go headless, unless you don't plan on doing any testing in the sim or accessing your ERA reports.

Plus, on linux I would be able to create a script that does everything for me when I start coding, and I don't know that much of windows cmd prompt...

Okay, but one of the nice things about WSL is that you don't have to use CMD or Powershell for anything if you don't want to.

A windows binary such as the Monkey C compiler doesn't know or care whether you launched it from Explorer, Eclipse, VS Code, cmd, powershell or WSL bash.... (I guess you do have to worry about interop issues like line endings and path formats).

Thank you very much for these advices, I think I'll stick with compiling on cmd prompt and getting RSA key with linux.

Do you know if there is a persistent way to write : 

> for /f usebackq %i in (%APPDATA%\Garmin\ConnectIQ\current-sdk.cfg) do set CIQ_HOME=%~pi

> set PATH=%PATH%;%CIQ_HOME%\bin

in cmd prompt with something like .bashrc of linux ?

No worries.

See:

https://ss64.com/nt/syntax-autoexec.html

superuser.com/.../run-a-script-on-start-up-on-windows-10

This may also be of interest:

devblogs.microsoft.com/.../