I use the SDK without Eclipse on centOS, but of course I cannot run the new sdk manager for download the SDK because I don't have graphical interface.
There is a link somewhere to download the sdk?
thx
I use the SDK without Eclipse on centOS, but of course I cannot run the new sdk manager for download the SDK because I don't have graphical interface.
There is a link somewhere to download the sdk?
thx
The problem is that there is no need for a GUI to use the SDK and devices, so why is one needed to download them?
The sdkmanager doesn't work for me anyway, but I can download the SDK by using https…
Of course I am.
Because I'm doing Continuous Integration. I'd like to let Github run the unit tests for me. You know, like every modern development project...
I completely agree to @9256409. I've set up a complete Continuous Integration toolchain for my Connect IQ development using GitHub Action and Docker images. To generate the Docker images a non-interactive mechanism to install the SDK, device files & fonts would be really helpful.
I agree with @9256409 as well. It should be easy to download the SDK and its dependencies. I lost far too much time trying to find the URLs of the SDK and the device specific bits required to setup a Docker image in order to do CI with my app.
Come on Garmin, we are in 2020, don't you know? We're living in a world with Docker and Continuous Integration. It's time to wake up.
Can't you just use a GUI to download the SDK and Devices and then copy them to the proper place in your image?
The SDK is the easy part BTW. The Devices/Fonts need to be in a specific place based on your OS/User.
And both the SDK and Devices/Fonts will be updated occasionally
@9256409: thx for the link to json, earlier I found xml.
3.1.9 is the last version with Direct Download, here are links to zip, for future reference:
I also prefer a zip version which can be easily used with a compile script, without installing anything.
One of my map app becomes actually useful only after adding user's images, so it needs recompiling from GitHub. I will need to change my instruction for that (probably I just link to older version), as current SDK page requires the manager with login which doesn't work on all systems and is more complicated.
3.1.9 is fairly old now as 3.2.4 is the current version. And if you stick with 3.1.9, you won't be able to build for any devices that have come out since then. The devices are separate since 3.2.0, but also downloaded with the SDK Manager.