Meson Build File For Issue: #78

[LinuxLegend]

The scope of this Meson Build project is to migrate from CMake to Meson build system and to ensure it have the same or comparable feature parities to that of CMake. There are few additional configuration options such as modifying VMA defines to affect the memory allocation behaviors in Vulkan and so forth. There are some clear advantages to this meson file being clearer to write and to be easily imported into another Meson-based projects and potentially CMake as well through Pkg-config manifest. Existing meson project can import declared dependencies such as vkvg_shared_dep and vkvg_static_dep.

Pending Tasks to Complete:

• GLSL Shader compilation and inclusion
• Test cases migration from cmake to meson
• Double check on everything to see if I got all of the options/defines sorted out
• Sort out the duplicate reference/functions in glutess for priorityq-heap.c file
• Add other VMA in-code defines (such as VMA_DEFAULT_LARGE_HEAP_BLOCK_SIZE)
• Add Readme Documentation on Meson configuration

[LinuxLegend]

Removed New Automated Test Cases for Validating VKVG Behaviors by comparing pixels to control group images, will make that a separate issue/pull request apart from this, but it would be useful in CI/CD considerations for evaluating regressions.

[LinuxLegend]

Test cases are now working properly and now onto GLSL shader compilation stage and inclusion.

[LinuxLegend]

Finished the shader compilation for both Linux/Windows, will have to test Windows later on. All that is left is documentation.

[LinuxLegend]

Also added test related option to hide the warnings from test cases, this is set to true by default (non-test code still have warnings displayed.)

[LinuxLegend]

All set for review!

[LinuxLegend]

Strict ansi exclusion is removed, for more info on what is going on: #78 (comment)

[jpbruyere]

one more level from 'building' (an additional '#'), also I would have preferred the meson build to appear after the original cmake. (at least for now).
The VMA options should be splited in a separated markdown file (in the doc folder).

[jpbruyere]

Is it possible to replace the shader/helper batches by commands directly issued from the meson build file?
The vkvg compilation options being the same in both cmake and meson, duplicating them in the readme is not the best solution.
Maybe, to simplify you work on this, you may create a complete separate markdown file for the meson build documentation with the actual content of your pr for the reame (in the doc forlder), I will add a link in the readme. Then We may move the compilation options in a generic paragraph for both compile method, and simply give some hint to use them for cmake and meson.

[jpbruyere]

I also guess vkh stuff (including vma) will be moved to the vkhelpers project?

[LinuxLegend]

Yep, there would still be some configuration options retained on this Vkvg project, that can be passed over to Vkh project for meson options.

[jpbruyere]

Thank you for your time on this...

[LinuxLegend]

I will reopen this PR when I get it cleaned up and hopefully getting confirmation from Tinycthread on the undefine line.