I submitted the question via contact form on developers.garmin.com, and Jenny responded with a suggestion I ask here. I'd like to tinker around, but having to use Eclipse in a Windows VM significantly increases friction. I know its a long shot, but I'd love to see your SDK reach a little wider audience. Any Linux love on the horizon?
Thanks for reaching out. I'd love to hear form some others on the forums too. What would the interest level in a Linux SDK be? What distros do you all use?
Thanks for reaching out. I'd love to hear form some others on the forums too. What would the interest level in a Linux SDK be? What distros do you all use?
Thanks for checking back in! I'm a Debian-based (mostly Ubuntu forks) guy, but I see a lot of cross-platform developer tools being released with both RPM and DEB packaging.
Same here. I asked the support as well, and got an answer that I should go ask in the forums.
Surprisingly, bash scripts are already present in the Windows version of the SDK. It's just missing the binaries [FONT=Courier New]shell[/FONT] and [FONT=Courier New]simulator[/FONT].
Personally, I use debian sid x64, but a statically compiled binary would be fine. Of course, a deb for precisely my distribution and the source code would be best, but for now, a tarball with statically compiled binaries would be sufficient for me, and would work on any Linux distribution.
[The forum software ate my post, I hope this gets through].
I asked the support as well, and was redirected here. Surprisingly, the Windows SDK already contains bash scripts, just the [FONT=Courier New]shell[/FONT] and [FONT=Courier New]simulator[/FONT] binaries are missing.
Personally, I use debian sid x64 - so a deb file would be optimal. For now, statically compiled binaries inside a tarball would do though, and that would work on all Linux distributions.
I've been using Kubuntu for years and started writing test apps for CIQ platform even before I get my F3. There is a page on the net about running the CIQ in wine in Linux and it's fairly functional. The issue is it has issues with 16 color display devices. For example even though I want to publish with the latest SDK release I hat to test with 1.2.1 for some of my apps. Otherwise I could get no functional color on screen or even the app terminates with errors.
Really interested in Linux SDK.
Actually, you can get everything working under linux. Just requires some tinkering and installing wine to run the simulator under and having the right version of Java (all the compiler stuff is java based, so any platform that runs Java can compile things -- only the simulator is platform specific).
I don't use eclipse (honestly, hate the environment), but have a few scripts that do my building, signing, etc and launch the simulator. If you're developing under linux, this isn't hard to get working (again, a few manual steps, like starting the simulator vs the eclipse plugin being able to). I've developed three working apps so far.
Bigger issue is that the simulator is not really a very good test for various watches -- lots of minor diffs between it and the real thing. But that isn't a linux thing ;-)
There is a good "bootstrap" on what you need to do to get this working under linux. It'll get you going in the right direction, though I do recall one or two obvious small changes that had to be made before it all worked.
Actually, you can get everything working under linux. Just requires some tinkering and installing wine to run the simulator under and having the right version of Java (all the compiler stuff is java based, so any platform that runs Java can compile things -- only the simulator is platform specific).
I don't use eclipse (honestly, hate the environment), but have a few scripts that do my building, signing, etc and launch the simulator. If you're developing under linux, this isn't hard to get working (again, a few manual steps, like starting the simulator vs the eclipse plugin being able to). I've developed three working apps so far.
Bigger issue is that the simulator is not really a very good test for various watches -- lots of minor diffs between it and the real thing. But that isn't a linux thing ;-)
There is a good "bootstrap" on what you need to do to get this working under linux. It'll get you going in the right direction, though I do recall one or two obvious small changes that had to be made before it all worked.
Thanks, Gerry. I also dislike Eclipse -- almost as much as I dislike hacking together fragile off-platform development environments out of duct tape and baling wire so they'll sortakindaifyouholdyourmouthright work under Linux. ;) There are lots of folks opening up their SDKs to native Linux developers; I'd love to see Garmin get on the bandwagon. I'm quite pleased with the response this has gotten so far, so I'm hopeful they'll see it as worthy of their development resources.
