Open streaksu opened 5 years ago
Currently we use a very small subset of the output from --cppflags
, as well as --libs
with --link-shared
or --link-static
You do need some of the cppflags to successfully link, but we try to throw away the ones that are bogus (thought it appears LLVM has stopped adding quite so much garbage to cppflags).
As for the C++ thing, we don't really have a good way in meson to signal that you are going to use the C API (and it's pretty limited compared to the C++ one), but I understand why you'd need the C interfaces from D.
The actual error you're running into looks like a legitimate bug though.
You are using a pretty old version of meson, and there has been a lot of work in the D compilers since then. Could you try 0.51.2 or master?
edit: fix typo
Using 0.51.2 fixes the meson error, but since the Cpp flags are passed for compilation to the D compiler in use, it just cannot compile.
Hello, my issue is the following: I wanted to use meson to build my D language project, a compiler targetting LLVM IR. LLVM has a C interface that requires no effort to use with some FFI, but meson doesnt really support this use, forcing cpp to be present in the languages of the compiler, but that is not the main issue. I would recommend having
llvm
using only the output ofllvm-config --libs
instead of the full flags reported for c and c++ compilers that I guess it currently uses.The main issue is that, when configuring a package in D that has
llvm
as dependency, and aadd_languages('cpp')
to silence the errors regarding this language not being present, one gets the following errors:that does not allow me to go any further.
Is there any way to do this with meson, is this a bug that has to be fixed? Thanks in advance!