Merge website and CMake to Meson transition

Building a website to structure and deploy the artifacts was planned and
requires a well set-up build system to handle all the file paths targets
and dependencies.

Since multiple CMake Zephyr builds are required for the application
firmware, bootloader firmware and the native_sim application firmware
simulation CMake external project was used.

Since this generates a build tree with a confusing structure Meson was
evaluated.

Finally the Meson build system was a good fit as top-level build system
and allows external projects as an experimental feature if they can
configure a Make-based build system which is given for Zephyr.

1 files changed, 27 insertions, 0 deletions

diff --git a/fw/sim/meson.build b/fw/sim/meson.build
new file mode 100644
index 0000000..a4dcb8a
--- /dev/null
+++ b/fw/sim/meson.build
@@ -0,0 +1,27 @@
+external_project = import('unstable-external_project')
+
+external_project.add_project(
+  configure_zephyr,
+  configure_options: [
+    '--source-tree', application_source,
+    '--build-tree', meson.current_build_dir() / 'build',
+    '--board', 'native_sim/native/64',
+    '--zephyr-base', zephyr,
+    '--zephyr-modules', ';'.join(zephyr_modules),
+  ],
+  verbose: true,
+)
+
+simulation = custom_target(
+  'simulation',
+  output: ['simulation-linux-amd64.exe'],
+  command: [
+    build_zephyr,
+    '--build-tree', meson.current_build_dir() / 'build',
+    '--binary-name', 'zephyr.exe',
+    '--target-name', 'simulation-linux-amd64.exe',
+  ],
+  build_by_default: true,
+  install: true,
+  install_dir: 'website/static',
+)