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, 42 insertions, 0 deletions

diff --git a/pcb/meson.build b/pcb/meson.build
new file mode 100644
index 0000000..7f8b85f
--- /dev/null
+++ b/pcb/meson.build
@@ -0,0 +1,42 @@
+schematic_files = [
+  'iot-contact.kicad_sch',
+  'contacts.kicad_sch',
+  'ethernet.kicad_sch',
+  'io.kicad_sch',
+  'power.kicad_sch',
+  'processor.kicad_sch',
+]
+
+schematic = custom_target('schematic',
+  output: ['schematic.pdf'],
+  command: [
+    'kicad-cli',
+    'sch',
+    'export',
+    'pdf',
+    '--output', meson.current_build_dir() / 'schematic.pdf',
+    meson.current_source_dir() / 'iot-contact.kicad_sch',
+  ],
+  depend_files: schematic_files,
+  build_by_default: true,
+  install: true,
+  install_dir: 'website/static',
+)
+
+bom = custom_target('bom',
+  output: ['bill-of-materials.csv'],
+  command: [
+    'kicad-cli',
+    'sch',
+    'export',
+    'bom',
+    '--fields',
+    'Reference,Description,Value,Footprint,Manufacturer,MPN,Datasheet',
+    '--output', meson.current_build_dir() / 'bill-of-materials.csv',
+    meson.current_source_dir() / 'iot-contact.kicad_sch',
+  ],
+  depend_files: schematic_files,
+  build_by_default: true,
+  install: true,
+  install_dir: 'website/static',
+)