Training/meson-test
1
0
Fork 0
Code Issues Pull requests Releases 1 Activity
Meson example with Poco and LibXML2.
6 commits 1 branch 1 tag 49 KiB
C++ 59.1%
Meson 38%
C 2.9%
Find a file
Yohan Boujon 710e6b743e Added readme and license.
2025-03-13 10:08:22 +01:00
include Added poco (cmake) dependency. 2025-03-12 10:44:47 +00:00
src Removed warnings for cmake poco. CMake defines fully working on newer version of meson. 2025-03-12 16:16:29 +01:00
subprojects Added poco (cmake) dependency. 2025-03-12 10:44:47 +00:00
.gitignore Added libxml2 depdency. 2025-03-12 10:29:39 +01:00
LICENSE Added readme and license. 2025-03-13 10:08:22 +01:00
meson.build Removed warnings for cmake poco. CMake defines fully working on newer version of meson. 2025-03-12 16:16:29 +01:00
README.md Added readme and license. 2025-03-13 10:08:22 +01:00

README.md

Meson Example

Static Badge Static Badge

Here is an example of a meson configuration using external libraries such as LibXML2 (Fully Meson-compatible) and Poco (Cmake subproject). For now it only builds on Linux and the prefered method is static linking because the output libraries name does not follow Poco CMake's standard. More on this can be addressed on the following issues:

Building

In the root directory launch the following:

meson build
cd build && meson compile

Why Meson instead of CMake ?

Meson is a new build system that aims to be less verbose than CMake. It uses Ninja as its backend which might be faster than make. Meson is considered cross-platform and its only drawback for now is its compatibility with other projects.

Comparing this repo with the cmake-fetch, we can see that for the same project we have way less configuration for the same result. Meson should be used for newer project, and newer project should learn to comply with this build system which would be the future of cross compilation.