Well allow me to retort. First off mhahn, when you originally posted the links to the IoT Devkit ... IT DIDN"T WORK. Yeah, the page loaded but the only version of the kit it would let me download was for Windows. I haven't had a windows machine in my lab for 20 years. Sorry but my wife won't let me do a bunch of techno-gangster mumbo-jumbo on her laptop which is the only machine within probably 10 miles of Prospect Hill, NC with any variant of Windows installed. So that was pretty much out. Since your links were about the 10th Rabbit Hole I had been down that week trying to get an environment working, I quickly moved on.
Now back to yesterday. My boss, longtime friend and mentor, following instructions from this site bricked his board. Now I've convinced him that Galileo is an incredible platform (and it is) for his project. That combined with my problems getting a set of tools that would work obviously doesn't engender a whole lot of confidence in the man, his 40 year love affair with all things Intel not withstanding.
Now I don't mean to be nasty but dood we just want an answer. Ok so you provided one. Again. This time I was able to download the IoTDevkit for Linux. Cool. And it almost works even. Of course nothing says "Oh by the way, the old 1.0.0 'Big Image' won't work with the toolkit, you actually need to get the image we built for it". I figured that one out for myself. Now I can build, transfer and even execute programs from Eclipse to/on my target. Awesome. Sadly though it's still broken:
dallas@Amelia:~/iotdk-ide-linux$ ./devkit-x86/sysroots/x86_64-pokysdk-linux/usr/bin/i586-poky-linux/i586-poky-linux-gdb --version
Traceback (most recent call last):
File "/home/dallas/iotdk-ide-linux/devkit-x86/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/site.py", line 569, in <module>
main()
File "/home/dallas/iotdk-ide-linux/devkit-x86/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/site.py", line 551, in main
known_paths = addusersitepackages(known_paths)
File "/home/dallas/iotdk-ide-linux/devkit-x86/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/site.py", line 278, in addusersitepackages
user_site = getusersitepackages()
File "/home/dallas/iotdk-ide-linux/devkit-x86/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/site.py", line 253, in getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
File "/home/dallas/iotdk-ide-linux/devkit-x86/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/site.py", line 243, in getuserbase
USER_BASE = get_config_var('userbase')
File "/home/dallas/iotdk-ide-linux/devkit-x86/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/sysconfig.py", line 524, in get_config_var
return get_config_vars().get(name)
File "/home/dallas/iotdk-ide-linux/devkit-x86/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/sysconfig.py", line 423, in get_config_vars
_init_posix(_CONFIG_VARS)
File "/home/dallas/iotdk-ide-linux/devkit-x86/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/sysconfig.py", line 302, in _init_posix
raise IOError(msg)
IOError: invalid Python installation: unable to open /home/dallas/iotdk-ide-linux/devkit-x86/sysroots/x86_64-pokysdk-linux/usr/include/python2.7/pyconfig.h (No such file or directory)
That is because there IS NO /home/dallas/iotdk-ide-linux/devkit-x86/sysroots/x86_64-pokysdk-linux/usr/include! Before you get all excited and say "Why were you executing gdb --version from the console?", it is because I couldn't copy the error output from eclipse to the clipboard and I didn't want to mess with a screenshot. But this is the identical error traceback.
So you want a constructive feature request? Ok:
1) Please provide an IDE that works. Like all of it. Not just part of it.
2) Please provide a comprehensive Howto for installing said IDE on Linux/Windows/OSx. I personally would settle for Linux
Want me to tell you whats missing from the kit that causes it not to meet my needs?
1) iotdk-ide-linux/devkit-x86/sysroots/x86_64-pokysdk-linux/usr/include/python2.7/pyconfig.h apparently.
I just want something that works. I don't want to futz with it all day (week/month/year) long. I (we) have applications to write, we don't care about the tools. Once upon a time Intel provided those things It was part of the program. It just worked. If it didn't, somebody from Intel would help you figure out why.
Honestly is that too much to ask?