Difference between revisions of "Setting up TUnit"
(New page: = Minimum Requirements = * [http://docs.tinyos.net/index.php/Main_Page#Installing_TinyOS Installation of the latest tinyos-2.x] * Check out a copy of the latest [http://tinyos.cvs.sourcef...) |
|||
Line 1: | Line 1: | ||
− | = Minimum Requirements = | + | == Minimum Requirements == |
* [http://docs.tinyos.net/index.php/Main_Page#Installing_TinyOS Installation of the latest tinyos-2.x] | * [http://docs.tinyos.net/index.php/Main_Page#Installing_TinyOS Installation of the latest tinyos-2.x] | ||
Line 25: | Line 25: | ||
For the remainder of this setup guide, I will assume your TinyOS is setup in the simplistic structure, with directories located at /opt/tinyos-2.x and /opt/tinyos-2.x-contrib. | For the remainder of this setup guide, I will assume your TinyOS is setup in the simplistic structure, with directories located at /opt/tinyos-2.x and /opt/tinyos-2.x-contrib. | ||
− | = Environment Variables = | + | == Environment Variables == |
− | = Classpaths = | + | == Classpaths == |
Revision as of 09:26, 10 January 2008
Minimum Requirements
- Installation of the latest tinyos-2.x
- Check out a copy of the latest tinyos-2.x-contrib repository (instructions here).
- Ant is completely optional, but may be used to generate nicer looking HTML reports.
Your projects and directories may differ. On the automated unit testing server, the tinyos-2.x and tinyos-2.x-contrib directories are located in a simplistic structure:
opt |-- tinyos-2.x |-- tinyos-2.x-contrib
In my own private projects, I prefer a more complex structure:
opt |-- myProject | |-- tinyos-2.x <-- A snapshot of TinyOS my project is compatible with | |-- tests | | |-- ... bunch of sub-test directories... | |-- tinyos-2.x-myProject <-- Project's files that override the TinyOS baseline | |-- tinyos-2.x-contrib
For the remainder of this setup guide, I will assume your TinyOS is setup in the simplistic structure, with directories located at /opt/tinyos-2.x and /opt/tinyos-2.x-contrib.