commit | 7bb985eeb0930905c2f4d551e895dd5293094931 | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Thu Sep 02 14:31:40 2021 -0700 |
committer | Ed Tanous <ed@tanous.net> | Wed Sep 08 22:00:36 2021 +0000 |
tree | ac273ab55e2302b49d8b3c003bad9b10e7ecca5d | |
parent | e62afa5995822679c0ca0ceaf7e4784e46f0b9c3 [diff] |
Include systemd and boost as system dependencies In practice, adding the include_type: 'system' causes the imports for these dependencies to be included in gcc as -Isystem instead of -I. In practice, this doesn't have much effect, but allows clang-tidy to correctly not flag errors in headers from system libraries, which causes the clang-tidy checks to succeed when run from within devshell. Tested: ran "bitbake -c devshell bmcweb" From within the shell, ran: cd oe-workdir/bmcweb-1.0+git999 ninja clang-tidy And observed that header errors no longer present. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I6f24f061a3f8a58c07ae64ebc82ffefe11c469a2
This component attempts to be a "do everything" embedded webserver for openbmc.
At this time, the webserver implements a few interfaces:
BMCWeb is configured by setting -D
flags that correspond to options in bmcweb/meson_options.txt
and then compiling. For example, meson <builddir> -Dkvm=disabled ...
followed by ninja
in build directory. The option names become C++ preprocessor symbols that control which code is compiled into the program.
meson builddir ninja -C builddir
meson builddir -Dbuildtype=minsize -Db_lto=true -Dtests=disabled ninja -C buildir
If any of the dependencies are not found on the host system during configuration, meson automatically gets them via its wrap dependencies mentioned in bmcweb/subprojects
.
meson builddir -Dwrap_mode=nofallback ninja -C builddir
meson builddir -Dbuildtype=debug ninja -C builddir
meson builddir -Db_coverage=true -Dtests=enabled ninja coverage -C builddir test
When BMCWeb starts running, it reads persistent configuration data (such as UUID and session data) from a local file. If this is not usable, it generates a new configuration.
When BMCWeb SSL support is enabled and a usable certificate is not found, it will generate a self-sign a certificate before launching the server. The keys are generated by the secp384r1
algorithm. The certificate
C=US, O=OpenBMC, CN=testhost
,SHA-256
algorithm.