{"action":"created","issue":{"url":"https://api.github.com/repos/jantje/hardware/issues/5","labels_url":"https://api.github.com/repos/jantje/hardware/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/jantje/hardware/issues/5/comments","events_url":"https://api.github.com/repos/jantje/hardware/issues/5/events","html_url":"https://github.com/jantje/hardware/issues/5","id":108118735,"number":5,"title":"Debugging and unit testing Arduino (Part 3) issues & comments","user":{"login":"pep","id":4065479,"avatar_url":"https://avatars.githubusercontent.com/u/4065479?v=3","gravatar_id":"","url":"https://api.github.com/users/pep","html_url":"https://github.com/pep","followers_url":"https://api.github.com/users/pep/followers","following_url":"https://api.github.com/users/pep/following{/other_user}","gists_url":"https://api.github.com/users/pep/gists{/gist_id}","starred_url":"https://api.github.com/users/pep/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pep/subscriptions","organizations_url":"https://api.github.com/users/pep/orgs","repos_url":"https://api.github.com/users/pep/repos","events_url":"https://api.github.com/users/pep/events{/privacy}","received_events_url":"https://api.github.com/users/pep/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-09-24T12:13:32Z","updated_at":"2015-09-26T12:00:48Z","closed_at":null,"body":"Hi Jantje,\r\nI tried to add a comment to Debugging and unit testing Arduino (Part 3) on you blog but I'm not a registered user.\r\nI have been following parts 1-3 and have had some issues with getting it to work. I've numbered my problems, so its easier to respond to each: \r\n\r\n1/ in your refactoring of the original BlinkWithoutDelay code you have lost the setup() routine of the pinMode(LED_BUILTIN, OUTPUT); and as a consequence the UNO led does not flash properly when downloaded to the board. \r\n2/ You added a EDIT Note about setting up the gcc compiler in your path capable of making local executables. \r\n3/ I loaded cygwin64 and set the windows path environment variable, but \r\n4/ the debug build has issues knowing where to get specific headers from and it seems to cause a clash between the arduino, jantje hardware and the cygwin header/libraries. \r\n5/ Or is MingW preferred to be used? ( I saw another person's comments as he was using MingW.)\r\n6/ Maybe some more detail about how to configure each build configuration would be helpful. \r\n7/ Also I assumed that the jantje hardware files needed to be installed in the private library/hardware path. \r\n8/ When will the next installment part 4 be available to show the unit testing with googletest? I noticed that gtest is in your jantje hardware files.\r\n9/ I noticed that eclipse-arduino IDE has the C/C++ unit testing support plugin component/view installed so I'm keen to see some examples of how to use it. I know you are quite busy.\r\n10/ Maybe we could use this project as a test project to the IDE test team, once it works fully? \r\nI'm sure everything will work it's just some of the steps aren't too obvious as to how to control the library usage between the windows compiler, Arduino and your library?\r\nRegards, Phil.\r\nphil.pidgeon@gmail.com"},"comment":{"url":"https://api.github.com/repos/jantje/hardware/issues/comments/143426875","html_url":"https://github.com/jantje/hardware/issues/5#issuecomment-143426875","issue_url":"https://api.github.com/repos/jantje/hardware/issues/5","id":143426875,"user":{"login":"pep","id":4065479,"avatar_url":"https://avatars.githubusercontent.com/u/4065479?v=3","gravatar_id":"","url":"https://api.github.com/users/pep","html_url":"https://github.com/pep","followers_url":"https://api.github.com/users/pep/followers","following_url":"https://api.github.com/users/pep/following{/other_user}","gists_url":"https://api.github.com/users/pep/gists{/gist_id}","starred_url":"https://api.github.com/users/pep/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pep/subscriptions","organizations_url":"https://api.github.com/users/pep/orgs","repos_url":"https://api.github.com/users/pep/repos","events_url":"https://api.github.com/users/pep/events{/privacy}","received_events_url":"https://api.github.com/users/pep/received_events","type":"User","site_admin":false},"created_at":"2015-09-26T12:00:48Z","updated_at":"2015-09-26T12:00:48Z","body":"If I use build all I get the errors previously mentioned. BUT, If I build the configurations separately and don't use build all, each one builds individually. In the post part3 where you perform the \"debug as\"->debug configurations then Select C/C++ application and new. when I do it sometimes there is already a debugDemo Debug C/C++ application already created, other times not,  but either way the path is Release\\debugDemo.elf NOT Debug\\debugDemo.elf because there is no .elf created in the Debug directory. Then when I press the debug button if it isn't greyed/out the debug session starts but ends with a Problem Occurred dialog 'Launching debugDemo Debug' has encountered a problem.\"Target request failed: Error creating process Release\\debugDemo.elf, (error 193)."}}