{"action":"created","issue":{"url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/1387","labels_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/1387/labels{/name}","comments_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/1387/comments","events_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/1387/events","html_url":"https://github.com/MarlinFirmware/Marlin/issues/1387","id":54794228,"number":1387,"title":"Should include instructions for how to add libraries in marlin","user":{"login":"NarimaanV","id":4958838,"avatar_url":"https://avatars.githubusercontent.com/u/4958838?v=3","gravatar_id":"","url":"https://api.github.com/users/NarimaanV","html_url":"https://github.com/NarimaanV","followers_url":"https://api.github.com/users/NarimaanV/followers","following_url":"https://api.github.com/users/NarimaanV/following{/other_user}","gists_url":"https://api.github.com/users/NarimaanV/gists{/gist_id}","starred_url":"https://api.github.com/users/NarimaanV/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/NarimaanV/subscriptions","organizations_url":"https://api.github.com/users/NarimaanV/orgs","repos_url":"https://api.github.com/users/NarimaanV/repos","events_url":"https://api.github.com/users/NarimaanV/events{/privacy}","received_events_url":"https://api.github.com/users/NarimaanV/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-01-19T17:58:39Z","updated_at":"2015-01-23T16:34:39Z","closed_at":null,"body":"After some debate in issue https://github.com/MarlinFirmware/Marlin/issues/1366, it seems something we should do now at least, regardless of whether or not its better to include libraries in Marlin or just add them to the IDE is to include some instructions in Marlin about how to do that for users who aren't familiar with adding libraries to Marlin (since they still have to run certain displays). I've already got a draft of the file to add to the documentation done and plan on adding some comments wherever it mentions to add the library to refer to that documentation, but I noticed something regarding the layout of the \"ArduinoAddons\" folder that I wanted to clarify before presenting the Pull Request. Within that \"ArduinoAddons\" folder, only the \"Arduino_0.0.x\" and \"Arduino_1.0.x\" folders have all the libraries you could need for Marlin (\"Arduino_1.5.x\" has one of the libraries buried deep in one of the sub folders but I don't think that entirely counts). So I'm wondering, is this intentional? Is there something about the 1.5.x versions of Arduino that doesn't need the libraries? Or should I just direct everyone to the \"Arduino_1.0.x\" folder regardless of what version they're using?"},"comment":{"url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/comments/71221083","html_url":"https://github.com/MarlinFirmware/Marlin/issues/1387#issuecomment-71221083","issue_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/1387","id":71221083,"user":{"login":"thinkyhead","id":698003,"avatar_url":"https://avatars.githubusercontent.com/u/698003?v=3","gravatar_id":"","url":"https://api.github.com/users/thinkyhead","html_url":"https://github.com/thinkyhead","followers_url":"https://api.github.com/users/thinkyhead/followers","following_url":"https://api.github.com/users/thinkyhead/following{/other_user}","gists_url":"https://api.github.com/users/thinkyhead/gists{/gist_id}","starred_url":"https://api.github.com/users/thinkyhead/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thinkyhead/subscriptions","organizations_url":"https://api.github.com/users/thinkyhead/orgs","repos_url":"https://api.github.com/users/thinkyhead/repos","events_url":"https://api.github.com/users/thinkyhead/events{/privacy}","received_events_url":"https://api.github.com/users/thinkyhead/received_events","type":"User","site_admin":false},"created_at":"2015-01-23T16:34:39Z","updated_at":"2015-01-23T16:34:39Z","body":"Yeah, just refer to the Configuration files generally. They can change over time and we won't have to keep updating the docs."}}