8 To get started developing with VPP, you need to get the required VPP sources and then build the packages.
9 For more detailed information on the build system please refer to :ref:`buildsystem`.
11 .. _makesureinstalled:
13 VPP for Ubuntu: Environment Setup
14 -------------------------------------------
16 If you are not downloading VPP on Ubuntu with WSL (Windows Subsystem for Linux), please disregard this section
17 and jump to 'Get the VPP Sources'.
19 Before starting on VPP for Ubuntu, make sure WSL2 and Ubuntu are installed.
21 To install WSL2 and Ubuntu, run Windows PowerShell as an administrator and enter this in the terminal:
23 .. code-block:: console
27 Next, go to the 'resolv.conf' file in Ubuntu's '/etc' folder.
28 It should have been automatically generated when Ubuntu was installed; if it doesn't exist, create it.
29 Please use 'sudo' to avoid "File resolv.conf is unwritable" errors.
31 .. code-block:: console
34 $ sudo nano resolv.conf
36 In the file, add the following content in place of the current 'nameserver X.X.X.X' line:
38 .. code-block:: console
42 This replaces the DNS nameserver on your machine with the Google DNS service,
43 resolving any DNS Internet connection issues.
45 Note: by default, the 'resolv.conf' file regenerates every time you restart Ubuntu, so your changes won't be saved.
46 To keep your changes, run the following command to make 'resolv.conf' immutable:
48 .. code-block:: console
50 $ sudo chattr +i /etc/resolv.conf
53 Now copy the following lines from 'resolv.conf':
55 .. code-block:: console
58 generateResolvConf = false
60 Then, go to the 'wsl.conf' file in '/etc' and paste the lines there.
61 Please use 'sudo' here as well to avoid "File wsl.conf is unwritable" errors.
63 .. code-block:: console
67 In order to test your DNS server connection, please ping 8.8.8.8 on the terminal:
69 .. code-block:: console
72 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
73 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=9.58 ms
74 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=45.8 ms
75 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=9.62 ms
76 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=11.4 ms
77 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=12.2 ms
78 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=8.69 ms
79 64 bytes from 8.8.8.8: icmp_seq=7 ttl=116 time=52.4 ms
80 64 bytes from 8.8.8.8: icmp_seq=8 ttl=116 time=11.0 ms
83 While still in /etc, run the following commands:
85 .. code-block:: console
88 $ sudo apt-get dist-upgrade
89 $ sudo apt-get install --reinstall ca-certificates
90 $ sudo update-ca-certificates
93 Finally, head back to your home directory and jump to 'Get the VPP Sources'.
98 --------------------------
100 Depending on the environment you are operating in, proxies may need to be set.
101 Run these proxy commands to specify the *proxy-server-name* and corresponding *port-number*:
103 .. code-block:: console
105 $ export http_proxy=http://<proxy-server-name>.com:<port-number>
106 $ export https_proxy=https://<proxy-server-name>.com:<port-number>
110 -----------------------------------
112 To get the VPP sources that are used to create the build, run the following commands:
114 .. code-block:: console
116 $ git clone https://gerrit.fd.io/r/vpp
119 Build VPP Dependencies
120 --------------------------------------
122 Before building a VPP image, make sure there are no FD.io VPP or DPDK packages
123 installed, by entering the following commands:
125 .. code-block:: console
128 $ dpkg -l | grep DPDK
130 There should be no output, or no packages shown after the above commands are run.
132 Please make sure **make** is installed before running the next command.
133 If it is not installed, run the following command first:
135 .. code-block:: console
137 $ sudo apt install make
139 Run the following **make** command to install the dependencies for FD.io VPP.
141 If the download hangs at any point, then you may need to
142 :ref:`set up proxies <setupproxies>` for the download to work.
144 .. code-block:: console
147 Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
148 Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
149 Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
150 Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
151 Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [803 kB]
152 Get:6 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [732 kB]
155 Update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jmap to provide /usr/bin/jmap (jmap) in auto mode
156 Setting up default-jdk-headless (2:1.8-56ubuntu2) ...
157 Processing triggers for libc-bin (2.23-0ubuntu3) ...
158 Processing triggers for systemd (229-4ubuntu6) ...
159 Processing triggers for ureadahead (0.100.0-19) ...
160 Processing triggers for ca-certificates (20160104ubuntu1) ...
161 Updating certificates in /etc/ssl/certs...
162 0 added, 0 removed; done.
163 Running hooks in /etc/ca-certificates/update.d...
169 ----------------------------
171 This build version contains debug symbols which are useful for modifying VPP. The
172 **make** command below builds a debug version of VPP. The binaries, when building the
173 debug images, can be found in /build-root/vpp_debug-native.
175 The Debug build version contains debug symbols, which are useful for troubleshooting
176 or modifying VPP. The **make** command below, builds a debug version of VPP. The
177 binaries used for building the debug image can be found in */build-root/vpp_debug-native*.
179 .. code-block:: console
182 make[1]: Entering directory '/home/vagrant/vpp-master/build-root'
183 @@@@ Arch for platform 'vpp' is native @@@@
184 @@@@ Finding source for dpdk @@@@
185 @@@@ Makefile fragment found in /home/vagrant/vpp-master/build-data/packages/dpdk.mk @@@@
186 @@@@ Source found in /home/vagrant/vpp-master/dpdk @@@@
187 @@@@ Arch for platform 'vpp' is native @@@@
188 @@@@ Finding source for vpp @@@@
189 @@@@ Makefile fragment found in /home/vagrant/vpp-master/build-data/packages/vpp.mk @@@@
190 @@@@ Source found in /home/vagrant/vpp-master/src @@@@
193 make[5]: Leaving directory '/home/vagrant/vpp-master/build-root/build-vpp_debug-native/vpp/vpp-api/java'
194 make[4]: Leaving directory '/home/vagrant/vpp-master/build-root/build-vpp_debug-native/vpp/vpp-api/java'
195 make[3]: Leaving directory '/home/vagrant/vpp-master/build-root/build-vpp_debug-native/vpp'
196 make[2]: Leaving directory '/home/vagrant/vpp-master/build-root/build-vpp_debug-native/vpp'
197 @@@@ Installing vpp: nothing to do @@@@
198 make[1]: Leaving directory '/home/vagrant/vpp-master/build-root'
200 Build VPP (Release Version)
201 -----------------------------------------
203 This section describes how to build the regular release version of FD.io VPP. The
204 release build is optimized and does not create any debug symbols.
205 The binaries used in building the release images are found in */build-root/vpp-native*.
207 Use the following **make** command below to build the release version of FD.io VPP.
209 .. code-block:: console
213 Installing External Dependencies
214 -------------------------------------------
215 At this point, there are still some VPP external dependencies left to install. They could be installed
216 using 'make-build', but this only installs them locally in the VPP tree, not in the operating system.
217 In order to fix this and save time, run the following command:
219 .. code-block:: console
221 $ make install-ext-deps
223 -------------------------------------------
224 Building Necessary Packages
225 -------------------------------------------
227 The package that needs to be built depends on the type system VPP will be running on:
229 * The :ref:`Debian package <debianpackages>` is built if VPP is going to run on Ubuntu
230 * The :ref:`RPM package <rpmpackages>` is built if VPP is going to run on Centos or Redhat
234 Building Debian Packages
235 ^^^^^^^^^^^^^^^^^^^^^^^^^
237 To build the debian packages, use the following command:
239 .. code-block:: console
245 Building RPM Packages
246 ^^^^^^^^^^^^^^^^^^^^^^^
248 To build the rpm packages, use one of the following commands below, depending on the system:
250 .. code-block:: console
254 Once the packages are built they can be found in the build-root directory.
256 .. code-block:: console
260 If the packages are built correctly, then this should be the corresponding output:
262 vpp_18.07-rc0~456-gb361076_amd64.deb vpp-dbg_18.07-rc0~456-gb361076_amd64.deb
263 vpp-dev_18.07-rc0~456-gb361076_amd64.deb vpp-api-lua_18.07-rc0~456-gb361076_amd64.deb
264 vpp-lib_18.07-rc0~456-gb361076_amd64.deb vpp-api-python_18.07-rc0~456-gb361076_amd64.deb
265 vpp-plugins_18.07-rc0~456-gb361076_amd64.deb
267 Finally, the created packages can be installed using the following commands. Install
268 the package that corresponds to OS that VPP will be running on:
272 .. code-block:: console
277 For Centos or Redhat:
279 .. code-block:: console