-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linker options in dyaml.pc not correct? #137
Comments
Both, actually, although GtkD is probably a bit more correct. In pkg-config files, we generally expect GCC/Clang compatible compiler flags, which makes the dyaml case correct. At the same time though, ldc and dmd are not fully compatible to GCC/Clang's arguments, therefore GtkD could be correct. What actually happens though is that at least when using Meson, Meson will transparently convert the flags to whatever the currently used D compiler is comfortable with, and AFAIK dub will do the same. |
OK. I am stuck with Dub and SCons for build since Meson cannot build Unit-Threaded stuff because there is no unitary build. (I just do a small hack for the SCons build which is irritating but I can cope.) |
Meson supports unity builds, but the D support likely doesn't. Implementing this should be easy though. DMD and LDC not following GCC/Clang flags is an incredible nuisance, so much so that we actually ship a script in Debian as part of the dlang debhelper support to work around this issue. |
The libgtkd-3-dev package on Debian Sid installs /usr/lib/x86_64-linux-gnu/pkgconfig/gtkd-3.pc:
which works for dmd and ldc2, I suspect perhaps not for gdc. D-YAML creates:
Which doesn't work fordmd or ldc2 without adding a -L in front of the Libs options. So who has it right GtkD or D-YAML?
The text was updated successfully, but these errors were encountered: