meson
cxx-static-shared-example
Our great sponsors
meson | cxx-static-shared-example | |
---|---|---|
110 | 12 | |
5,257 | 32 | |
2.1% | - | |
9.8 | 0.0 | |
1 day ago | over 2 years ago | |
Python | CMake | |
Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
meson
-
Which Build Tool for a Bootstrappable Project?
[1]: https://github.com/mesonbuild/meson/issues/8153
-
Building Waybar fails
The Meson build system Version: 1.2.3 Source dir: /home/patrik/workspace/Waybar Build dir: /home/patrik/workspace/Waybar/build Build type: native build Project name: waybar Project version: 0.9.24 C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-5) 13.2.0") C linker for the host machine: cc ld.bfd 2.41 C++ compiler for the host machine: c++ (gcc 13.2.0 "c++ (Debian 13.2.0-5) 13.2.0") C++ linker for the host machine: c++ ld.bfd 2.41 Host machine cpu family: x86_64 Host machine cpu: x86_64 Compiler for C++ supports link arguments -lc++fs: NO Compiler for C++ supports link arguments -lc++experimental: NO Compiler for C++ supports link arguments -lstdc++fs: YES Program git found: YES (/usr/bin/git) WARNING: You should add the boolean check kwarg to the run_command call. It currently defaults to false, but it will default to true in future releases of meson. See also: https://github.com/mesonbuild/meson/issues/9300 Has header "filesystem" : YES Checking if "nl_langinfo with _NL_TIME_WEEK_1STDAY, _NL_TIME_FIRST_WEEKDAY" : links: YES Run-time dependency threads found: YES Found pkg-config: /usr/bin/pkg-config (1.8.1) Run-time dependency fmt found: YES 9.1.0 Run-time dependency spdlog found: YES 1.12.0 Run-time dependency wayland-client found: YES 1.22.0 Run-time dependency wayland-cursor found: YES 1.22.0 Run-time dependency wayland-protocols found: YES 1.32 Run-time dependency gtkmm-3.0 found: YES 3.24.8 Run-time dependency dbusmenu-gtk3-0.4 found: YES 16.04.0 Run-time dependency gio-unix-2.0 found: YES 2.78.1 Run-time dependency jsoncpp found: YES 1.9.4 Run-time dependency sigc++-2.0 found: YES 2.12.1 Found CMake: /usr/bin/cmake (3.27.7) Run-time dependency libinotify found: NO (tried pkgconfig and cmake) Run-time dependency epoll-shim found: NO (tried pkgconfig and cmake) Run-time dependency libinput found: YES 1.23.0 Run-time dependency libnl-3.0 found: YES 3.7.0 Run-time dependency libnl-genl-3.0 found: YES 3.7.0 Run-time dependency upower-glib found: YES 1.90.2 Run-time dependency libpipewire-0.3 found: YES 0.3.85 Run-time dependency playerctl found: YES 2.4.1 Run-time dependency libpulse found: YES 16.1 Run-time dependency libudev found: YES 252 Run-time dependency libevdev found: YES 1.13.1 Run-time dependency libmpdclient found: YES 2.20 Run-time dependency xkbregistry found: YES 1.6.0 Run-time dependency jack found: YES 0.126.0 Run-time dependency wireplumber-0.4 found: YES 0.4.15 Library sndio found: YES Checking for function "sioctl_open" with dependency -lsndio: YES Run-time dependency gtk-layer-shell-0 found: YES 0.8.1 Run-time dependency systemd found: YES 252 Computing int of "__cpp_lib_chrono" : 201611 Configuring waybar.service using configuration Run-time dependency cava found: NO (tried pkgconfig and cmake) Looking for a fallback subproject for the dependency cava Executing subproject cava cava| Project name: cava cava| Project version: 0.9.1 cava| C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-5) 13.2.0") cava| C linker for the host machine: cc ld.bfd 2.41 cava| Has header "iniparser.h" : NO cava| Has header "iniparser4/iniparser.h" : NO Message: cava is not found. Building waybar without cava subprojects/cava-0.9.1/meson.build:65:3: ERROR: Problem encountered: iniparser library is required A full log can be found at /home/patrik/workspace/Waybar/build/meson-logs/meson-log.txt WARNING: Running the setup command as `meson [options]` instead of `meson setup [options]` is ambiguous and deprecated.
-
How to find a list of all gcc errors/warnings?
As it happens, I recently landed a PR in meson to add a clang-like Weverything mode that includes all of that, so you can get a minimal list of more or less all GCC warnings, organized by version, from the meson source here: https://github.com/mesonbuild/meson/blob/710a753c78077220b13a9f7e999dcdb61339efb1/mesonbuild/compilers/mixins/gnu.py
-
Makefile Tutorial
Came here to post the same. The answer for How to build software? is Meson[1] for C and C++ and also other languages. Works well on Windows and Mac, too.
I’ve written a small Makefile to learn the basic and backgrounds. Make is fine. But the next high-level would have been Autotools, which is an intimidating and weird set of tools. Most new stuff written in C/C++ use now Meson and it feels sane.
[1] https://mesonbuild.com
-
CMake x make?
If you are very fortunate, you'll be able to choose something else. I like meson myself: it looks a bit like python, it's popular, small, simple, well-documented, easy to install and update, and it works well everywhere.
-
C++ Papercuts
I suggest changing the build tool. Meson improved C and C++ a lot:
https://mesonbuild.com/
The dependency declaration and auto-detection is nice. But the hidden extra is WrapDB, built-in package management (if wanted):
https://mesonbuild.com/Wrap-dependency-system-manual.html
-
A Modern C Development Environment
> C's only REAL problem (in my opinion) which is the lack of dependency management. Most everything else can be done with a makefile and a half decent editor.
Care to hear about our lord and saviour Meson?
Both of your quoted problems are mutually incompatible: dependency management isn't the job of the compiler, it's a job for the build or host system. If you want to keep writing makefiles, be prepared to write your own `wget` and `git` invocations to download subprojects.
Meanwhile, Meson solves the dependency management problem in a way that makes both developers and system integrators/distributions happy. It forces you to make a project that doesn't have broken inter-file or header dependency chains and cleans up all the clutter and cruft of a makefile written for any non-trivial project, while making it trivial to integrate other meson projects into your build, let other people integrate your project into theirs, and provides all of the toggles and environment variables distribution developers need to package your library properly. You can really have your cake and eat it too.
https://mesonbuild.com/
-
cgen: another declarative CMake configuration generator
Other people going down this route seem to end up writing cmake replacements instead. I'm thinking of something like meson here except that meson never intended to transpile to cmake.
- Makefile vs Cmake - Objective comparison ?
-
Installer script for CMake, Ninja, and Meson
I thought I would share my custom installer script for the latest GitHub versions of CMake, Ninja, and Meson.
cxx-static-shared-example
-
How does one just "create a library, package, or tool" ?
Anyone can create a library using cmake-init. This example goes into a little more detail and while it's for C++, the very same things apply sans a single target property on the library.
-
CMake template for C++ library (static/shared & Windows/Linux) project
Thanks, I noticed a project friendlyanon/cxx-static-shared-example that have feature I didn't used.
-
how can I make a dynamic library using cmake?
https://github.com/friendlyanon/cxx-static-shared-example explains how to do libraries correctly, https://github.com/friendlyanon/cmake-init gives you a template that's ready to go. If something is not clear, ask away.
-
Beginner Question: How do I link a shared library (DLL) with my game's executable?
Here is an example going deeper into how to create a shared library using CMake: https://github.com/friendlyanon/cxx-static-shared-example You'd have to do these regardless of CMake, this just shows how to do it with it.
-
A comprehensive resource for making libraries?
This example is more focused on explaining on the what and why.
-
CPack builds too much
Or if you are also packaging .deb then you're going to need a toolchain anyway, you can put these variables there as well.
-
I am trying to replace CMake with c++
To learn how to write a CML that is ideally written to be easy for both consumers building the library, developers developing the library and consumers vendoring the library via add_subdirectory (which will be a very very important thing to do in the near future), please check out this educational example repository https://github.com/friendlyanon/cxx-static-shared-example
-
Ive created a github repo showcasing modern, target based, cmake projects
This repo will show you how to make your project CML for an easy to (re)use library that supports packaging.
-
Nuke for C++
CMake's what you want. You need to know how separation of concerns applies when it comes the lists files. Resources in general suck, the CMake docs are not really discoverable, but are very good otherwise. You can get a handle of how things are supposed to be put together here.
-
CLion IDE
cxx-static-shared-example - 50 lines for requirements + however many for sources + 60 for install rules: now this is a library that builds some artifacts. Still extremely simple and straightforward.
What are some alternatives?
CMake - Mirror of CMake upstream repository
Sharpmake - Sharpmake is an open-source C#-based solution for generating project definition files, such as Visual Studio projects and solutions, GNU makefiles, Xcode projects, etc.
ninja - a small build system with a focus on speed
ccls - C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting
SCons
FunctionalPlus - Functional Programming Library for C++. Write concise and readable C++ code.
Bazel - a fast, scalable, multi-language and extensible build system
HMake - C++ build system that uses C++ for build configuration.
cmake-init - The missing CMake project initializer
prorab - :construction_worker: non-recursive GNU make-based build framework
BitBake - The official bitbake Git is at https://git.openembedded.org/bitbake/. Do not open issues or file pull requests here.