vibe-core
vibe-core copied to clipboard
vibe-d
WIP: Add Meson support
When vibe-core was split off vibe.d itself, Meson support was broken. This adds it back in, based of the original Meson code when it was in the vibe.d project.
Should be a step towards resolving https://github.com/vibe-d/vibe.d/issues/2531
Depends on: https://github.com/vibe-d/eventcore/pull/171
Right now, some of the unit tests seem to be broken. I have no idea what causes it, which is why this is marked as WIP:
chris@roku ~/Code/D/vibe-core/build (git)-[master] % ninja test
[0/1] Regenerating build files.
The Meson build system
Version: 0.57.1
Source dir: /home/chris/Code/D/vibe-core
Build dir: /home/chris/Code/D/vibe-core/build
Build type: native build
Project name: Vibe Core
Project version: 1.13.1
D compiler for the host machine: ldc2 (llvm 1.25.0 "LDC - the LLVM D compiler (1.25.0):")
D linker for the host machine: ldc2 ld.gold 2.36.1
Host machine cpu family: x86_64
Host machine cpu: x86_64
Dependency eventcore found: YES 0.9.13 (cached)
Dependency stdx-allocator found: YES 3.0.1 (cached)
Build targets in project: 2
Found ninja-1.10.2 at /usr/bin/ninja
[0/1] Running all tests.
1/1 vibe-test_core FAIL 0.13s killed by signal 6 SIGABRT
>>> MALLOC_PERTURB_=44 /home/chris/Code/D/vibe-core/build/vibe-test_core
―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
stderr:
core.exception.AssertError@../source/vibe/core/args.d(57): readOption() may only be called once per option name.
----------------
??:? _d_assert_msg [0x7f6cf44fe649]
args.d:57 bool vibe.core.args.readOption!(bool).readOption(immutable(char)[], bool*, immutable(char)[]) [0x555eab07defa]
log.d:920 void vibe.core.log.initializeLogModule() [0x555eab1775ee]
core.d:1529 void vibe.core.core._sharedStaticCtor_L1520_C1() [0x555eab1355bc]
??:? int rt.minfo.rt_moduleCtor().__foreachbody1(ref rt.sections_elf_shared.DSO) [0x7f6cf453d448]
??:? int rt.sections_elf_shared.DSO.opApply(scope int delegate(ref rt.sections_elf_shared.DSO)) [0x7f6cf453e578]
??:? rt_init [0x7f6cf4533457]
??:? void rt.dmain2._d_run_main2(char[][], ulong, extern (C) int function(char[][])*).runAll() [0x7f6cf45339dc]
??:? _d_run_main2 [0x7f6cf4533837]
??:? _d_run_main [0x7f6cf453368d]
??:? [0x555eab07d214]
??:? __libc_start_main [0x7f6cf411cb24]
??:? [0x555eab07d10d]
uncaught exception
core.exception.AssertError@../source/vibe/core/core.d(1600): No more threads registered
----------------
??:? _d_assert_msg [0x7f6cf44fe649]
core.d:1600 void vibe.core.core._staticDtor_L1582_C1() [0x555eab135fa3]
??:? void rt.minfo.ModuleGroup.runTlsDtors() [0x7f6cf453d0e9]
??:? _d_dso_registry [0x7f6cf453f160]
??:? [0x7f6cf4d71aad]
??:? [0x7f6cf4eee23a]
??:? [0x7f6cf4134696]
??:? exit [0x7f6cf413483d]
??:? __libc_start_main [0x7f6cf411cb2b]
??:? [0x555eab07d10d]
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
I cannot get the unit tests to work on Meson for some reason, would anyone be able to help me out with that? Or would omitting the unit test be fine for Meson builds?
Or would omitting the unit test be fine for Meson builds?
IMO it would be fine to omit as long as it doesn't prevent testing Meson. In other words, can we still get a CI in place that builds some working executable ?
What error are you seeing ?
@HenkKalkwater Hi! I am interested in Meson too
Why we use import('pkgconfig') here?
@HenkKalkwater Hi! I am interested in Meson too
Why we use
import('pkgconfig')here?
Very likely because I want to generate a pkgconfig file for this library (it is used further below) and it seems to work. If I'm not mistaken, this is needed so that other projects can find this library to set the correct linker flags and so on.
Ok, I just not sure at 100% in that tradition
It looks like other Meson projects can use any other Meson project directly (as subproject) without additional 3-rd party formats like pkgconfig, cmake, etc
Ok, I just not sure at 100% in that tradition
It looks like other Meson projects can use any other Meson project directly (as subproject) without additional 3-rd party formats like pkgconfig, cmake, etc
Yes, Meson is able to do so. Generating pkg-config files enables Meson and other build systems to find it when it is installed on the system on Unix-like systems and perhaps Windows, but I'm not sure about that.
Ok, I added wrap files into my project and tried to setup Meson and catched:
subprojects/taggedalgebraic/meson.build:19:0: ERROR: Recursive include of subprojects: vibe_d => vibe-core => eventcore => taggedalgebraic => eventcore.
I think we must carefully rewrite from scratch every meson.build of vibe.d dependencies with using of all Meson modern changes and without unnecessary directives before we can proceed.
Also I started to make dub2meson tool (https://github.com/denizzzka/dub2meson/)
It isn't able to be compiled for now - need patched DUB.
For now it isn't able to convert whole vibe.d, but vibe.d is very important to build with Meson because from vibe.d depend about 1/3 of all packages. This is why I want to propose to (re)write meson.build files for Vibe.d and all of its dependencies.
According to dub.sdl taggedalgebraic isn't have any dependency
I just messed-up URLs