= GCI Hello World Task =


[[TOC(GCI/HelloWorld, depth=2)]]

This task consists of following the instructions at [wiki:GSoC/GettingStarted GSOC Getting Started] and helping improve the instructions.

We prefer you use a GNU/Linux distribution if possible, as these tend to be the best supported.
=== Directions for Students ===

Follow the instructions at https://devel.rtems.org/wiki/GSoC/GettingStarted **EXCEPT**:

 *  Use your favorite GNU/Linux distribution.
  *  [http://www.virtualbox.org Virtualbox] images are available which should give you more options (http://virtualboximages.com/) including using a Windows computer to run a virtual machine with GNU/Linux.
 *  Build your own tools using the [wiki:Developer/Tools/RSB RTEMS Source Builder (RSB)]
 *  '''Report back on the process''' to help us improve the [wiki:GSoC/GettingStarted GSoC Getting Started] page to be current, clear, and correct.
 *  '''Submit a git patch''' [https://devel.rtems.org/wiki/Developer/Git/Users#CreatingaPatch HowTo create git patch] to your GCI claimed task (GCI website).
 *  Fill in an entry in the Feedback table below.
 * If you run into trouble, ask for help on the [wiki:TBR/Website/RTEMSMailingLists RTEMS Users mailing list], [wiki:Developer/IRC IRC channel], or use Google to search for similar problems others may have experienced before.
=== Feedback ===

Note: Some sample feedback from previous years is included.

||'''Student''' || '''Host OS''' || '''RTEMS Target''' || '''Feedback'''
|| Bryan D. || Arch Linux || sparc-rtems4.11 || While compiling the tools and RTEMS I only encountered two problems. The first one was with binutils; for some reason, it refused to compile outside the source directory, so I compiled it in the source directory. The second problem was with building RTEMS itself. The error was easy to fix though and just required removing the --disable-posix flag when calling ./configure.
|| Kevin F. || Linux Mint 13 LTS || sparc-rtems4.11 || I made lots of errors myself, but overall the instructions were fairly clear. Perhaps the RSB Quick Start should explain moving executables a bit more (like where to find them) and the RTEMS Quick Start should have remarked that you should put export the PATH to the tools bin you compiled. I needed python2.7-dev installed.
|| Evan M. || Ubuntu || sparc-rtems4.11 || I found the directions straightforward, although I do admit I had some trouble from time to time. It also seemed like several pages contradicted each other, but that might have been on my side due to my lack of experience. 
|| Kkvazar Q. || Fedora 20 || sparc-rtems4.11 || I wasn't able to finish the task, because I got lost in the documentation, the pages weren't well related and were contradicting. Some useful pages weren't easy to find such as the git README. I expected sb-check to tell me about missing devel libs, but it didn't. 'bootstrap' was hard to find and it failed on missing files. Most of the questions I had were asked online, but weren't answered.
|| Ralph H. || Linux Mint 17.1 || sparc-rtems4.11 || Instructions were very clear and simple to follow, albeit spread over several pages. Compiling RBS was simple, with the error messages clear (I only had to install CSV). Finding information was easy, and compilation was successful first time (with slight modifications to certain paths to match my projects directory path). I should probably note that I likely had most of the dependencies for compiling RBS, etc. already as I had previously manually built a cross-targeted GCC (and so I was already aware of such things as adding targeting executables to the path, as well as using git relatively proficiently, thus I did not need to locate information on such topics). The source tree of RTEMS is simple to navigate, and there were no issues with rebuilding and debugging/running a modified executable.