Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Changes between Version 10 and Version 11 of GCI/Coding/HelloWorld


Ignore:
Timestamp:
12/24/15 20:23:19 (9 years ago)
Author:
Owen_8
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GCI/Coding/HelloWorld

    v10 v11  
    3232|| Alex S. || Debian Jessie (64-bit) ||  sparc-rtems4.11 || The documentation was straightforward and easy to follow, but at first the source tree of RTEMS can be confusing, and the architecture-specific tools need to be exported to your {{{PATH}}} to be readily used. The directions for building RBS were harder to follow than for RTEMS. ''Note for future newcomers: compiling with {{{-j`nproc`}}} will significantly speed up your build on multi-core hosts.''
    3333|| Michał P. || Arch Linux || sparc-rtems4.11 || Instructions were relly easy to follow, I had no problem building RTEMS. Unfortunatelly, RSB scripts assume that {{{/usr/bin/python}}} is {{{python2}}}, but that's an issue with nearly every build script and it's easy to solve, so it was not a big problem.
    34 || Owen P. || Ubuntu || sparc-rtems4.11 || Instructions were relatively clear, but at sometimes seemed vague to me. I had a few errors when trying to build the tool set with RSB, so I had to dig around in the log files multiple times. Overall, it was a fairly straightforward process to me.
     34|| Owen P. || Ubuntu and OS X || sparc-rtems4.11 || When I built RTEMS the first time on Ubuntu, I thought the instructions were relatively clear, but at sometimes seemed vague to me. I had a few errors when trying to build the tool set with RSB, so I had to dig around in the log files multiple times. When I built RTEMS on OS X, it didn't take long and I found it much easier than doing it on Ubuntu, probably because I already had experience. I was able to get it working the first time.