The gtkd-3.pc file on Debian Sid has:
Libs: -L-L/usr/lib/x86_64-linux-gnu/ -L-lgtkd-3 -L-ldl
doesn't this assume dmd or ldc. Won't the leading -L be a problem for gdc?
On 24-06-18 12:21, Russel Winder wrote:
The gtkd-3.pc file on Debian Sid has:
Libs: -L-L/usr/lib/x86_64-linux-gnu/ -L-lgtkd-3 -L-ldl
doesn't this assume dmd or ldc. Won't the leading -L be a problem for gdc?
If the GtkD library is compiled with gdc the generated pkg-config file
won't have the leading -L. And since the different compilers aren't
binary compatible that shouldn't be a problem.
I guess the problem I am thinking of is that there is only one file but two compilers. This implies that there ought to be compiler specific versions installed. Perhaps though this is just a Debian/Fedora/… problem. They assume one and only one pc file per library.
There is also the issue that Meson compiled D libraries are not dong the same as GtkD, hence the question. The canonical Meson pc file does not have the -L prefix on library flags.
On 25-06-18 16:35, Russel Winder wrote:
I guess the problem I am thinking of is that there is only one file but two compilers. This implies that there ought to be compiler specific versions installed. Perhaps though this is just a Debian/Fedora/… problem. They assume one and only one pc file per library.
There is also the issue that Meson compiled D libraries are not dong the same as GtkD, hence the question. The canonical Meson pc file does not have the -L prefix on library flags.
Until the compilers become binary compatible, the same issue exists for
the library its self. Debian and Fedora build there libraries with ldc,
when installing a copy of GtkD net to the one from the distro it will
need a compiler suffix on the pc file and the library fot things to work
properly.
pc files generated by meson do indeed not include the extra -L
irregardless of the compiler used. While this isn't a problem for build
tools it can be troublesome when building manually, i don't know what
would be the best way to handle this.