Enable Meson Build System & remove cmake support

- This commit enables the support for meson build system for
  bmcweb and also remove the cmake support

- The inital thought of migrating to meson build system was based
  on [link](https://mesonbuild.com/Simple-comparison.html)

- Other things to praise about meson are its simplicity and userfriendly ness.
  It also have native support for modern tools such as precompiled headers,
  coverage, Valgrind , unity builds e.t.c

- This commit also support the automatic download and setup of dependencies
  if they are not found in usual places using meson wraps that are already
  available in [wrap db](https://wrapdb.mesonbuild.com/)

- For few dependencies like boost, boost-url which does not have meson
  wrap support yet, i have misused the meson subproject command to download
  boost & boot-url and build against them if they are not found in usual
  places.

- For boost & boost-url the subproject command will always fail as meson
  supports other meson projects as subprojects but it will always download
  the source, and since we dont actually build boost/boost-url but just use
  the the source headers this should not be a problem.

- Cmake options removed:

   - BUILD_STATIC_LIBS has been removed as it is not being used any where as per the
     review comments.

-  By default the meson wraps are enabled and it downloads the dependencies if they
   are not found, and via bitbake this behaviour is disabled by default as download
   fallback feature is disabled.

- This commit also adds the README, changes for bmcweb as well.

- The meta-* layer changes are also pushed and marked as WIP under bmcweb_meson_port
  topic.

Tested By :
===========
1. Compilation is passed without error or warning in both arm & x86 sdks that
   are populated by yocto.
2. The unittests are also passed on both x86 & arm machines.
3. Compilation passed with various build types supported by meson (debug,debugoptimized,
   relase)
4. modified the meta-phosphor & meta-ibm to leverage meson build for bmcweb, and loaded
   the resulted image on qemu & real machine, checked the bmcweb status and was also able
   to pull the web-gui on both.
5. Tested few common commands related to session service & network service manually on a
   real machine and also also had run a CT regression bucket, and it looked clean.

The binary sizes when bmcweb is compiled via bitbake(using meta-ibm) are :
cmake: 3100080 bytes approx (3 MB)
meson: 2822596 bytes approx (2.7 MB)

1:1 equivalent hash is not possible due to couple of things:
1. The build types in meson does not have a 1:1 mapping with cmake build types.
2. Meson adds below mentioned compiler & linker flags than cmake as a part of
   warning_level & build types

CXXFLAGS :' -O2 -pipe -g -feliminate-unused-debug-types -fdiagnostics-color=always
            -D_FILE_OFFSET_BITS=64 -Winvalid-pch -DNDEBUG'
LDFLAGS : ' -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--no-undefined,-Wl,--end-group'

Tried to match the compile commands in both cmake & meson as much as possible and this
is what i could get.I have attached the compile_commands.json for both duing an yocto
full build in the [link](https://gofile.io/d/gM80fw) for reference.

Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Ia65689fdacb8c398dd0a019258369b2442fad2f3

1 files changed, 34 insertions, 0 deletions

diff --git a/meson_options.txt b/meson_options.txt
new file mode 100644
index 0000000000..e808f46a03
--- /dev/null
+++ b/meson_options.txt
@@ -0,0 +1,34 @@
+option('pam', type: 'feature', value : 'enabled', description : 'Built static libraries')
+option('yocto-deps', type: 'feature', value: 'disabled', description : 'Use YOCTO dependencies system')
+option('kvm', type : 'feature',value : 'enabled', description : 'Enable the KVM host video WebSocket.  Path is \'/kvm/0\'.  Video is from the BMC\'s \'/dev/video\' device.')
+option ('tests', type : 'feature', value : 'enabled', description : 'Enable Unit tests for bmcweb')
+option('vm-websocket', type : 'feature', value : 'enabled', description : '''Enable the Virtual Media WebSocket. Path is \'/vm/0/0\'to open the websocket. See https://github.com/openbmc/jsnbd/blob/master/README.''')
+option('vm-nbdproxy', type: 'feature', value : 'disabled', description : 'Enable the Virtual Media WebSocket.')
+option('rest', type : 'feature', value : 'enabled', description : '''Enable Phosphor REST (D-Bus) APIs. Paths directly map Phosphor D-Bus object paths, for example, \'/xyz/openbmc_project/logging/entry/enumerate\'. See https://github.com/openbmc/docs/blob/master/rest-api.md.''')
+option('redfish', type : 'feature',value : 'enabled', description: 'Enable Redfish APIs.  Paths are under \'/redfish/v1/\'. See https://github.com/openbmc/bmcweb/blob/master/DEVELOPING.md#redfish.')
+option('host-serial-socket', type : 'feature', value : 'enabled', description : 'Enable host serial console WebSocket. Path is \'/console0\'.  See https://github.com/openbmc/docs/blob/master/console.md.')
+option('static-hosting', type : 'feature', value : 'enabled', description : 'Enable serving files from the \'/usr/share/www\' directory as paths under \'/\'.')
+option('redfish-bmc-journal', type : 'feature', value : 'disabled', description : 'Enable BMC journal access through Redfish. Paths are under \'/redfish/v1/Managers/bmc/LogServices/Journal\'.')
+option('redfish-raw-peci', type : 'feature', value : 'disabled', description : '''Enable PECI transactions through Redfish. Paths are under \/redfish/v1/Systems/system/LogServices/CpuLog/Actions/Oem/CpuLog.SendRawPeci\'.''')
+option('redfish-cpu-log', type : 'feature', value : 'disabled', description : '''Enable CPU log service transactions through Redfish. Paths are under \'/redfish/v1/Systems/system/LogServices/Crashdump'.''')
+option('redfish-sysdump-log', type : 'feature', value : 'disabled', description : '''Enable System dump log service transactions through Redfish. Paths are under \'/redfish/v1/Systems/system/LogServices/SystemDump\''')
+option('redfish-dbus-log', type : 'feature', value : 'disabled', description : 'Enable DBUS log service transactions through Redfish. Paths are under \'/redfish/v1/Systems/system/LogServices/EventLog/Entries\'')
+option('redfish-provisioning-feature', type : 'feature', value : 'disabled', description : 'Enable provisioning feature support in redfish. Paths are under \'/redfish/v1/Systems/system/\'')
+option('bmcweb-logging', type : 'feature', value : 'disabled', description : 'Enable output the extended debug logs')
+option('mutual-tls-auth', type : 'feature', value : 'enabled', description : '''Enables authenticating users through TLS client certificates. The insecure-disable-ssl must be disabled for this option to take effect.''')
+option('ibm-management-console', type : 'feature', value : 'disabled', description : 'Enable the IBM management console specific functionality. Paths are under \'/ibm/v1/\'')
+option('http-body-limit', type: 'integer', min : 0, max : 30, value : 30, description : 'Specifies the http request body length limit')
+
+# Insecure options. Every option that starts with a `insecure` flag should
+# not be enabled by default for any platform, unless the author fully comprehends
+# the implications of doing so.In general, enabling these options will cause security
+# problems of varying degrees
+
+option ('insecure-disable-csrf', type : 'feature', value : 'disabled', description : 'Disable CSRF prevention checks.Should be set to false for production systems.')
+option ('insecure-disable-ssl', type : 'feature', value : 'disabled', description : 'Disable SSL ports. Should be set to false for production systems.')
+option ('insecure-disable-auth', type : 'feature', value : 'disabled', description : 'Disable authentication on all ports. Should be set to false for production systems')
+option ('insecure-disable-xss', type : 'feature', value : 'disabled', description : 'Disable XSS preventions')
+option ('insecure-tftp-update', type : 'feature', value : 'disabled', description : '''Enable TFTP based firmware update transactions through Redfish UpdateService.SimpleUpdate.''')
+option ('insecure-push-style-notification',type : 'feature', value : 'disabled', description : 'Enable HTTP push style eventing feature')
+option ('validate-unsecure-feature', type : 'feature', value : 'disabled', description : '''Enables unsecure features required by validation. Note: mustbe turned off for production images.''')
+option ('insecure-sensor-override', type : 'feature', value : 'disabled', description : 'Enables Sensor override feature without any check.')