aboutsummaryrefslogtreecommitdiffstats
path: root/resources/libraries
diff options
context:
space:
mode:
authorMiroslav Miklus <mmiklus@cisco.com>2016-03-14 17:54:58 +0100
committerMiroslav Miklus <mmiklus@cisco.com>2016-03-14 17:55:02 +0100
commit04d4f8210c7ae2e6a7b51abd060b8f734eecd05a (patch)
tree700c10caf6e5afb256d5f2db33e23adb3fcf97d3 /resources/libraries
parentbe157c8643a2c095d169e3ea78e8db60000189eb (diff)
tools: vpp download and installation script
Download and install 'RELEASE' version of vpp packages Dependecies: curl, dpkg, md5sum Change-Id: I894c8181125b84df3057afc092ed01c0a837321a Signed-off-by: Miroslav Miklus <mmiklus@cisco.com>
Diffstat (limited to 'resources/libraries')
0 files changed, 0 insertions, 0 deletions
n class="sb">`make` targets that may be of interest. To see the available targets run: make ### Quick-start: Vagrant 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 since its performance will never match that of bare metal; if your work is timing or performance sensitive, consider using bare metal in addition or instead of the VM. For this to work you will need a working installation of Vagrant. Instructions for this can be found [on the Setting up Vagrant wiki page] (https://wiki.fd.io/view/DEV/Setting_Up_Vagrant). ## More information Several modules provide documentation, see @subpage user_doc for more end-user-oriented information. Also see @subpage dev_doc for developer notes. Visit the [VPP wiki](https://wiki.fd.io/view/VPP) for details on more advanced building strategies and other development notes. ## Test Framework There is PyDoc generated documentation available for the VPP test framework. See @ref test_framework_doc for details.