![\"eclipse_show_project_button\"](\"https:\/\/raspberry-projects.com\/pi\/wp-content\/uploads\/2012\/10\/eclipse_show_project_button.png\")
<\/a>\n<\/p>\n\nConfigure it as follows, by right clicking the project name in the Project Explorer and selecting properties:
\nC\/C++ Build > Environment\n<\/p>\n
- \n
- \nAdd a variable named CYGWIN with value nodosfilewarning (tick 'add to all configurations')\n<\/li>\n
- \nAppend the following to the beginning of the PATH variable: c:\\cygwin\\opt\\cross\\x-tools\\arm-unknown-linux-gnueabi\\bin;c:\\cygwin\\bin;\n<\/li>\n<\/ul>\n
\nC\/C++ Build > Tool Chain Editor\n<\/p>\n
- \n
- \nSelect Cygwin GCC from Current toolchain dropbox.\n<\/li>\n<\/ul>\n
\nC\/C++ Build > Settings > Tool Settings\n<\/p>\n
- \n
- \nSet the Command field in Cygwin C++ Compiler to: arm-unknown-linux-gnueabi-g++\n<\/li>\n
- \nAdd an include path (not include files) in Includes which points to: c:\\cygwin\\opt\\cross\\x-tools\\arm-unknown-linux-gnueabi\\arm-unknown-linux-gnueabi\\sysroot\\usr\\include\n<\/li>\n<\/ul>\n
- \n
- \nSet the Command field in Cygwin C Compiler to: arm-unknown-linux-gnueabi-g++\n<\/li>\n
- \nAdd an include path (not include files) in Includes which points to: c:\\cygwin\\opt\\cross\\x-tools\\arm-unknown-linux-gnueabi\\arm-unknown-linux-gnueabi\\sysroot\\usr\\include\n<\/li>\n<\/ul>\n
- \n
- \nSet the Command field in Cygwin C++ Linker to: arm-unknown-linux-gnueabi-g++\n<\/li>\n
- \nAdd a library search path (not Libraries) in Libraries which points to: c:\\cygwin\\opt\\cross\\x-tools\\arm-unknown-linux-gnueabi\\arm-unknown-linux-gnueabi\\sysroot\\usr\\lib\n<\/li>\n<\/ul>\n
\nC\/C++ Build > Settings > Build Steps\n<\/p>\n
- \n
- \nSet the Command field in Post-build steps to: C:\/eclipse\/deployment_scripts\/rpi_deploy_debug.bat $(OutDir)${ProjName}.a "\/home\/pi\/projects\/${ProjName}.a"\n<\/li>\n
- \nAdd the description field to: Our auto deploy to RPi using putty script\n<\/li>\n<\/ul>\n
\nC\/C++ Build > Settings > Build Artifact\n<\/p>\n
- \n
- \nSet Artifact Extension to: a\n<\/li>\n<\/ul>\n
\nPress OK\n<\/p>\n
\nCompiling
\n<\/h5>\n\n(Tested with Eclipse V4.2 Juno)
\nProject > Build All (or Project > Build Project if "Build All" is not available)\n<\/p>\n\nThe project should compile without errors at this point.\n<\/p>\n
\nProblems
\n<\/h5>\n- \n
- \nIf the PuTTY window hangs just close it and confirm the close session box if it asks if you are sure. This is not a problem and putty remains working in the background.\n<\/li>\n
- \nTrying running eclipse by right clicking eclipse.exe and selecting 'Run as administrator'.\n<\/li>\n
- \nIf you get \/usr\/bin\/sh: g++: command not found errors you can right click the project > Properties > C\/C++ Build > Discovery Options and turn off 'Automate discovery of paths and symbols for both of the Cygwin tools listed. However this shouldn't be necessary.\n<\/li>\n
- \nIf you get other errors then go through and check the previous steps have been followed precisely.\n<\/li>\n
- \nOpening workspace project not shown – you may need to press this button to see the project:
\n<\/a>\n<\/li>\n- \nEclipse can be buggy. Try restarting it, or closing it then creating a new project to see if the problem magically vanishes (it sometimes does!).\n<\/li>\n<\/ul>\n
\nIf everything went smoothly select the Console output view in Eclipse and it should have printed something about the binary uploading and command execution.\n<\/p>\n
\nProblems
\n<\/h5>\n\nDelete the file on the RPi and then re-build\n<\/p>\n
\nHangs with PuTTY window open – just close it (it still runs in the background)\n<\/p>\n
\nDebugging With Eclipse
\n<\/h4>\n\nThe following is a re-workign of our original non working instructions following the solution found by <\/em>ChristianM – thanks Christian!\n<\/p>\n
\nCreating A Remote Connection
\n<\/h5>\n\nIf you've not proviously created a remote connection called remote_rpi (you can look in Menu > Window > Show View > Other > Remote Systems > Remote Systems) then create one first:\n<\/p>\n
\nMenu > File > New > Other > Remote System Explorer > Connection
\nSSH Only
\nHost name: The IP address of the RPi
\nConnection name: remote_rpi
\nRest default (just press finish)\n<\/p>\n\nSetup Debugging
\n<\/h5>\n\nNow setup a Debug Configuration.
\nSelect Menu Run > Debug configurations from the top menu.
\nRight click on C\/C++ Remote Application and choose New to add a new configuration.\n<\/p>\n\nMain tab\n<\/p>\n
- \n
- \nSet "C\/C++ Application field" to the name of the produced binary: Debug\/${project_name}.a\n<\/li>\n
- \nSelect Disable auto build.\n<\/li>\n
- \nClick on Select other…, near the left of the Apply button. From the newly opened window, choose GDB (DSF) Automatic Remote Debugging Launcher and click ok.\n<\/li>\n
- \nRemote Absolute File Path for C\/C++ Application: Set to the path where the application will be running on the Raspberry, e.g. \/home\/pi\/projects\/my_project.a (you can't use ${ProjName} or ${project_name} here)\n<\/li>\n
- \n"Connection:" drop down box: Select the "remote_rpi" connection you made.\n<\/li>\n<\/ul>\n
\nDebugger tab\n<\/p>\n
- \n
- \nSet the GDB debugger field to the path of the gdb which is part of our downloaded tool chain, so: c:\\cygwin\\opt\\cross\\x-tools\\arm-unknown-linux-gnueabi\\bin\\arm-unknown-linux-gnueabi-gdb.exe\n<\/li>\n<\/ul>\n
\nSource tab\n<\/p>\n
- \n
- \nAdd > Path mapping.\n<\/li>\n
- \nName it "Cygwin C Drive" and in Compilation Path enter: \/cygdrive\/c\/\n<\/li>\n
- \nIn Local file system path enter: C:\\\n<\/li>\n<\/ul>\n
\nClick on Apply and then Close. \n<\/p>\n
\n \n<\/p>\n
\nTo leave the debug perspective (mode) use Window > Open Perspective > C\/C++
\nTo come back use Window > Open Perspective > Debug
\n \n<\/p>\n\nTo Debug your project select "Debug" from the Menu > Run > Debug Configurations, or Menu > Run > Debug Histroy > rpi Debug\n<\/p>\n
\nProblems
\n<\/h5>\n\nDelete the file on the RPi and then re-build\n<\/p>\n
\nSetup Required On The Raspberry Pi
\n<\/h4>\n\nIn the "C\/C++ Build > Settings > Build Steps" step above the target for the putty transfer is set to "\/home\/pi\/projects\/${ProjName}.a". You need to create this \/projects\/ directory on the RPi for the project .a file to be transferred into, so use this at the RPi command line:\n<\/p>\n
\r\n
mkdir projects<\/code><\/pre>\n
- \nSet the GDB debugger field to the path of the gdb which is part of our downloaded tool chain, so: c:\\cygwin\\opt\\cross\\x-tools\\arm-unknown-linux-gnueabi\\bin\\arm-unknown-linux-gnueabi-gdb.exe\n<\/li>\n<\/ul>\n
- \nEclipse can be buggy. Try restarting it, or closing it then creating a new project to see if the problem magically vanishes (it sometimes does!).\n<\/li>\n<\/ul>\n
- \nSet Artifact Extension to: a\n<\/li>\n<\/ul>\n
- \nSelect Cygwin GCC from Current toolchain dropbox.\n<\/li>\n<\/ul>\n