Skip to content
Snippets Groups Projects
Commit ed5eedd8 authored by bbartels's avatar bbartels
Browse files

Update README.md

parent bcf79449
No related branches found
No related tags found
No related merge requests found
...@@ -16,7 +16,9 @@ implementation the "virtual quad". This is done in `src/virt_quad`. ...@@ -16,7 +16,9 @@ implementation the "virtual quad". This is done in `src/virt_quad`.
## Building ## Building
To build the libraries: ### Primarily Libraries and Executables
To build the libraries and executables:
``` ```
make make
``` ```
...@@ -27,9 +29,13 @@ directories: ...@@ -27,9 +29,13 @@ directories:
cd src/<project> && make cd src/<project> && make
``` ```
To build the XSDK project, use the XSDK IDE. Source the proper XSDK files, and **NOTE**: All build artifacts will be placed in `quad/lib` or `quad/bin`
then start up the XSDK IDE. Be sure to select the `xsdk_workspace` directory (depending on whether it is a library or executable, respectively)
in the quad directory as your "workspace":
### XSDK Project (what runs on the Zybo)
To build the XSDK project, use the XSDK IDE. Refer to the [Xilinx How-to](doc/how_to_use_xilinx_tools.pdf)
for more instructions. Be sure to select the `xsdk_workspace` directory in the
quad directory as your "workspace."
## Testing ## Testing
...@@ -41,6 +47,9 @@ Run the unit and functional tests: ...@@ -41,6 +47,9 @@ Run the unit and functional tests:
make test make test
``` ```
And glad to hear you are interested in writing your own unit tests! Look at the
README and examples in our simple testing library at `src/test`.
### Manually testing the hardware interface ### Manually testing the hardware interface
Of course, we cannot run automated tests on code that needs the Zybo. But Of course, we cannot run automated tests on code that needs the Zybo. But
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment