RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

2011-10-31 Joel Sherrill <joel.sherrill@oarcorp.com>

Browse Source 
PR 1947/doc
	* started/buildrt.t: Make note that native toolset is needed to
	configure and build RTEMS.
This commit is contained in:
Joel Sherrill
2011-10-31 13:46:43 +00:00
parent c652dfe261
commit b009f48110
2 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/ChangeLog
View File

@@ -1,3 +1,9 @@
2011-10-31 Joel Sherrill <joel.sherrill@oarcorp.com>
PR 1947/doc
* started/buildrt.t: Make note that native toolset is needed to
configure and build RTEMS.
2011-10-05 Joel Sherrill <joel.sherrill@oarcorp.com> 2011-10-05 Joel Sherrill <joel.sherrill@oarcorp.com>
Petr Benes <benesp16@fel.cvut.cz> Petr Benes <benesp16@fel.cvut.cz>

6
doc/started/buildrt.t
View File

@@ -156,6 +156,12 @@ disabled. Your application does not have to use networking but it must
be enabled. Thus the RTEMS configuration for a GNAT/RTEMS environment be enabled. Thus the RTEMS configuration for a GNAT/RTEMS environment
MUST include the @code{--enable-posix --enable-networking} flag. MUST include the @code{--enable-posix --enable-networking} flag.
@b{NOTE}: Building RTEMS requires that a few support programs be compiled
natively. This means there must be a native toolchain installed on your
development host. You will need to have a native compiler such as @i{gcc}
or @i{cc} in your execution path. If you cannot compile, link and execute
a native hello world program, then you will be unable to build RTEMS.
The following shows the command sequence required to configure, The following shows the command sequence required to configure,
compile, and install RTEMS with the POSIX API, FreeBSD TCP/IP, compile, and install RTEMS with the POSIX API, FreeBSD TCP/IP,
and C++ support disabled. RTEMS will be built to target and C++ support disabled. RTEMS will be built to target