Added some configuration options (not implemented)

docs/developers/ideas/path-finding.md

@@ -9,6 +9,7 @@ If it fails, check for any the following in such order:
 - `name.vs`
 - `name.xml`
 - `name.wasm`
+- `name.[arch].so` | `name.[arch].dll` | `name.[arch].dylib`
 - `name.so` | `name.dll` | `name.dylib`
 - `name.c`
 - `name.md`
@@ -18,6 +19,7 @@ If it fails and the folder `name` exists, check for these ones:
 - `name/main.vs`
 - `name/main.xml`
 - `name/main.wasm`
+- `name/main.[arch].so` | `name/main.[arch].dll` | `name/main.[arch].dylib`
 - `name/main.so` | `name/main.dll` | `name/main.dylib`
 - `name/main.c`
 - `name/main.md`

include/cbindings/vs.h

@@ -1,4 +1,16 @@
 #pragma once
+/**
+ * @file vs.h
+ * @author karurochari
+ * @brief Entrypoint for the C interface of `libvs`
+ * @details `libvs` is meant to be used via its C++ interface, and only a subset 
+ *          of its functionality is exposed via these bindings.  
+ *          Basically, what is needed to handle `ui_tree`s, access to the constrained 
+ *          interface ui widgets have, resolving paths, symbols and little more.
+ * @copyright Copyright (c) 2024
+ * 
+ */
+
 /*
     vs-fltk is a library meant to be used with its C++ interface.  
     Only a subset of its functionality is exposed with proper C bindings.  

meson.options

@@ -1 +1,14 @@
-option('tests', type: 'boolean', value: true)
+option('tests', type: 'boolean', value: true)
+
+option('use_curl', type: 'boolean', value: true)
+
+option('use_tcc', type: 'boolean', value: true)
+option('use_quickjs', type: 'boolean', value: true)
+option('use_wamr', type: 'boolean', value: true)
+
+# Only one between lua and luajit should be enabled
+option('use_lua', type: 'boolean', value: true)
+option('use_luajit', type: 'boolean', value: true)
+
+# If present, else build it manually
+option('use_system_fltk', type: 'boolean', value: true)