Build with RSB - I got lost.
joel.sherrill at oarcorp.com
Thu Mar 26 14:37:33 UTC 2015
On 03/26/2015 09:29 AM, Stanisław Grzeszczak wrote:
> I'm a newcomer to RTEMS. The GSoC/GettingStarted
> <https://devel.rtems.org/wiki/GSoC/GettingStarted> and Quick_Start
> <https://devel.rtems.org/wiki/TBR/UserManual/Quick_Start> pages led me
> to the RSB. I've followed the RSB
> <https://docs.rtems.org/rsb/> instructions and built the toolset and
> RTEMS using the --with-rtems option. Now, I wanted to get back to the
> GSOC/GettingStarted and Quick_Start instructions.
> Question 0: Should I still run the bootstrap, configure and make
> scripts, or did the RSB run them?
The RSB process built you the tools for an architecture -- like sparc or
arm. Now you
have to put those tools at the head of your PATH and build RTEMS for a
board (e.g. BSP) within that architecture.
So the RSB did not touch RTEMS itself. You do need to configure and
> Both tutorials mention testing the build by running a gdb session on a
> test program. I tried to build the "Hello" example with gcc; however,
> sparc-rtems4.11-gcc is unable to find the necessary header files. I
> tried sparc-rtems4.11-cpp -v and the include paths do not match the
> locations where rtems.h, rtems/test.h and others can be found.
> Q 1: Do the mismatched paths mean that the build went wrong? Or should
> I just fix the paths by hand, or move the lib/include folders?
> (Q 2: Should the examples have already been built along with
> everything else?)
If you configured and built RTEMS using configure, make, etc and
--enable-tests=samples, the executable was there and has symbolic
information in it.
I have no idea what you did. If you used a native gcc or tried to
compile it by hand,
then it didn't work.
> I'd appreciate any help regarding my questions. Should I include any
> additional information?
Maybe if this didn't help.
> Thank you,
-- Joel Sherrill
Ask me about RTEMS: a free RTOS
Support and Training Available
More information about the users