commit | 58e42b189dedd843f721b3a1c943f95ede0b2ca7 | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Sun Aug 22 15:04:10 2021 -0700 |
committer | Ed Tanous <ed@tanous.net> | Wed Sep 22 17:04:23 2021 +0000 |
tree | 0c60f185941c7f2123703f44bd7715bd71501140 | |
parent | ac7e1e0baf7fd0439b0352954d354f5f1a51e439 [diff] |
Disable nlohmann exceptions Nlohmann json gives the option to disable exceptions through a flag documented here: https://json.nlohmann.me/home/exceptions/ While we don't really use nlohmann exceptions in practice, disabling this flag saves us about 5k in compressed binary size, for probably no impact. Tested: Code compiles, binary size change seen locally. redfishtool -S Always -A Session -u root -p 0penBmc -vvvvvvvvv -r 192.168.7.2 raw GET /redfish/v1/Managers/bmc Returns the managers resource. Given that it both parses and encodes json, that would prove that nlohmann is working properly. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I68cba1628434d050379daca9bc39e4c3d724012b
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.