build-root | Build output directory
doxygen | Documentation generator configuration
dpdk | DPDK patches and build infrastructure
-@ref plugins | Not-yet-relocated VPP bundled plugins directory
@ref src | VPP source code
@ref src/plugins | VPP bundled plugins directory
@ref src/svm | Shared virtual memory allocation library
@ref src/vpp-api | VPP application API bindings
@ref src/vppinfra | VPP core library
test | Unit tests
-@ref vpp-api | Not-yet-relocated API bindings
-
+@ref src/vpp/api | Not-yet-relocated API bindings
+@ref src/examples | VPP example code
## Getting started
build script. This should be performed a non-privileged user with `sudo`
access from the project base directory:
- ./build-root/vagrant/build.sh
+ ./extras/vagrant/build.sh
If you want a more fine-grained approach because you intend to do some
development work, the `Makefile` in the root directory of the source tree
### Quick-start: Vagrant
-The directory `build-root/vagrant` contains a `VagrantFile` and supporting
+The directory `extras/vagrant` contains a `VagrantFile` and supporting
scripts to bootstrap a working VPP inside a Vagrant-managed Virtual Machine.
This VM can then be used to test concepts with VPP or as a development
platform to extend VPP. Some obvious caveats apply when using a VM for VPP
Visit the [VPP wiki](https://wiki.fd.io/view/VPP) for details on more
advanced building strategies and development notes.
+
+
+## Test Framework
+
+There is PyDoc generated documentation available for the VPP test framework. See @subpage test_framework_doc for details.