RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity

substitute folder with directory

Browse Source
This commit is contained in:
Ludwig Ortmann 2014-01-22 19:10:43 +01:00
parent 944be85124
commit a4a1c39d95
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -59,7 +59,7 @@ To create a bridge and two (or count at your option) tap interfaces:
./tapsetup.sh create [count]
### EXAMPLE APPLICATIONS
In the `examples` folder you can find some example applications. The `default` application demonstrates all available features for the current platform.
In the `examples` directory you can find some example applications. The `default` application demonstrates all available features for the current platform.
For example, you can use it to the test the native networking by running the `bin/default-native.elf` twice with two different tap interfaces as parameters, e.g. tap0 and tap1. Now configure two different addresses for both RIOT instances by typing `addr 1` and `addr 2`accordingly and send a text message from one "node" to another by typing `txtsnd 2 hello` on the first "node".

8
doc/doxygen/src/mainpage.txt
View File

@ -53,11 +53,11 @@
* The `boards` directory provides the configurations and initialization code for
* supported IoT platforms. In `core` you can find the kernel, while `cpu`
* comprises microcontroller specific implementations like startup and exception
* handling code. The folder `dist` contains a template for an application's Makefile
* handling code. The directory `dist` contains a template for an application's Makefile
* and external utilities like the terminal program `pyterm` or a script to build
* your own toolchain for ARM microcontrollers. Not very surprisingly you will find
* the (doxygen) documentation in `doc` and peripheral driver code in `drivers`.
* The `examples` folder provides some exemplary applications, `pkg` includes
* The `examples` directory provides some exemplary applications, `pkg` includes
* Makefiles to integrate external libraries into RIOT, and `sys` system libraries
* as well as the implementation of the network stacks which are located in
* `sys/net`. Finally, the subdirectory `tests` contains test applications,
@ -75,7 +75,7 @@
* * RIOTBASE
*
* and an instruction to include the `Makefile.include`, located in RIOT's root
* folder. `PROJECT` should contain the (unique) name of your project, `BOARD`
* directory. `PROJECT` should contain the (unique) name of your project, `BOARD`
* specifies the platform the project should be built for by default, and
* `RIOTBASE` specifies the path to your copy of the RIOT repository (note, that
* you may want to use `$(CURDIR)` here, to give a relative path). You can use Make's
@ -93,7 +93,7 @@
* communication to the device. Neither this variable nor the targets `flash` and
* `term` are mandatory for the native port.
*
* Some RIOT folders contain special Makefiles like `Makefile.base`,
* Some RIOT directories contain special Makefiles like `Makefile.base`,
* `Makefile.include` or `Makefile.dep`. The first one can be included into other
* Makefiles to define some standard targets. The files called `Makefile.include`
* are used in `boards` and `cpu` to append target specific information to

2
release-2014.01.txt
View File

@ -56,7 +56,7 @@ Further Changes
the RIOT repository itself
* full refactoring of the network stack and introducing a substructure
according to the modules' functionalities
* cleaned up Makefile system and simplified binary folder
* cleaned up Makefile system and simplified binary directory
* more documentation
* various bug fixes and cleanups