{"action":"created","issue":{"url":"https://api.github.com/repos/pfalcon/esp-open-sdk/issues/32","labels_url":"https://api.github.com/repos/pfalcon/esp-open-sdk/issues/32/labels{/name}","comments_url":"https://api.github.com/repos/pfalcon/esp-open-sdk/issues/32/comments","events_url":"https://api.github.com/repos/pfalcon/esp-open-sdk/issues/32/events","html_url":"https://github.com/pfalcon/esp-open-sdk/pull/32","id":60650850,"number":32,"title":"Add submodule for esptool-ck and adjust Makefile for it","user":{"login":"bluesceada","id":1301652,"avatar_url":"https://avatars.githubusercontent.com/u/1301652?v=3","gravatar_id":"","url":"https://api.github.com/users/bluesceada","html_url":"https://github.com/bluesceada","followers_url":"https://api.github.com/users/bluesceada/followers","following_url":"https://api.github.com/users/bluesceada/following{/other_user}","gists_url":"https://api.github.com/users/bluesceada/gists{/gist_id}","starred_url":"https://api.github.com/users/bluesceada/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bluesceada/subscriptions","organizations_url":"https://api.github.com/users/bluesceada/orgs","repos_url":"https://api.github.com/users/bluesceada/repos","events_url":"https://api.github.com/users/bluesceada/events{/privacy}","received_events_url":"https://api.github.com/users/bluesceada/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-03-11T12:27:29Z","updated_at":"2015-03-12T09:38:28Z","closed_at":"2015-03-11T14:53:57Z","pull_request":{"url":"https://api.github.com/repos/pfalcon/esp-open-sdk/pulls/32","html_url":"https://github.com/pfalcon/esp-open-sdk/pull/32","diff_url":"https://github.com/pfalcon/esp-open-sdk/pull/32.diff","patch_url":"https://github.com/pfalcon/esp-open-sdk/pull/32.patch"},"body":"This adds the esptool-ck as submodule and in Makefile (only \"esptool\", written in C).\r\nIt might need discussion, as I know this is somewhat a competitive software to the esptool.py, but it is\r\n1. still used by many projects to build the firmware bin files from elf, while esptool.py is used for flashing\r\n2. it was more recently updated and seems to consider support for flashing more boards in the future (see \"Support for NodeMCU board is coming up.\")\r\n\r\nI am new to the esp8266, so I might be wrong with this. The community seems to be still quite unsure about these tools?"},"comment":{"url":"https://api.github.com/repos/pfalcon/esp-open-sdk/issues/comments/78448722","html_url":"https://github.com/pfalcon/esp-open-sdk/pull/32#issuecomment-78448722","issue_url":"https://api.github.com/repos/pfalcon/esp-open-sdk/issues/32","id":78448722,"user":{"login":"pfalcon","id":500451,"avatar_url":"https://avatars.githubusercontent.com/u/500451?v=3","gravatar_id":"","url":"https://api.github.com/users/pfalcon","html_url":"https://github.com/pfalcon","followers_url":"https://api.github.com/users/pfalcon/followers","following_url":"https://api.github.com/users/pfalcon/following{/other_user}","gists_url":"https://api.github.com/users/pfalcon/gists{/gist_id}","starred_url":"https://api.github.com/users/pfalcon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pfalcon/subscriptions","organizations_url":"https://api.github.com/users/pfalcon/orgs","repos_url":"https://api.github.com/users/pfalcon/repos","events_url":"https://api.github.com/users/pfalcon/events{/privacy}","received_events_url":"https://api.github.com/users/pfalcon/received_events","type":"User","site_admin":false},"created_at":"2015-03-12T09:38:28Z","updated_at":"2015-03-12T09:38:28Z","body":"> but you are trying to give a direction with esp-open-sdk, thanks.\r\n\r\nWell, I decided put together esp-open-sdk exactly after seeing all the mess and duplication happening - just for my own sanity and for those few who may appreciate it.\r\n\r\n> Just currently most people (at least projects linked at http://esp8266.com/wiki ) do not really care and just install this even outdated 0.0.2 esptool debian package for making the bin images.\r\n\r\nThere 2 issues: a) \"most people do not care\" - and you can't change that, so I for example target few who care; b) \"outdated 0.0.2 esptool debian package\" - the one to blame is whoever put that binary package there (and possibly, whoever made it), my \"solution\" - don't provide any binary packages, target people who can, and are interested, to work with source. Also, if there's a choice, prefer high-level, easy to hack code, like Python, instead of written-for-obfuscation C mess.\r\n\r\n> I will try to make some updates to that wiki later on, if I get access, or is there any better centralized source for the esp8266 that I just didn't find?\r\n\r\nI have a strange feeling about esp8266,com . It surely helped to get initial efforts going somewhat coordinated. But it seems to be run by people who don't really do any hacking themselves, but like to get credit for community efforts (they *are* esp8266.com). I got confirmation to that doubt when they put mt6260.com up (which is empty, because providing content is much more harder than shelling out few dollars for a domain name). So, I personally prefer to communicate here, on github, with specific people who do the hacking.\r\n\r\nBut don't take that as discouragement - someone (who has time) should try to update info on esp8266.com wiki, as that's still where most new people will look for info.\r\n"}}