Bug 105112 - windows: libdir variant for static linking
Summary: windows: libdir variant for static linking
Alias: None
Product: pkg-config
Classification: Unclassified
Component: src (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: pkg-config
QA Contact:
Depends on:
Reported: 2018-02-15 14:20 UTC by Clemens Buchacher
Modified: 2018-08-25 12:53 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Clemens Buchacher 2018-02-15 14:20:17 UTC

I am cross-compiling https://github.com/cliffordwolf/icestorm.git for Windows 10 using mingw-w64 inside WSL (cross-compiling is what upstream has been doing, so I am trying to reuse that work). I already compiled the libftdi library dependency.

Upstream and others (https://rqou.com/jenkins/job/open-fpga-tools/job/icestorm-win64/691/console) seem to be hard-coding the libftdi library path to their install locations. I could be doing the same, but the icestorm Makefile already uses pkg-config, so we could make this work out of the box.

The problem is that libdir in libftdi1.pc points to $PREFIX/bin, rather than the lib directory, because shared libraries (DLLs) are typically installed in the same directory with the executable on Windows (they must be in the PATH or in the same directory with the executable for the dynamic linker to find it). The static library, however, is still installed in $PREFIX/lib.

What would you think about adding an optional alternative libdir, e.g. libdir_static, to indicate the location of static libraries, in case they are different from the location of the dynamic libraries?
Comment 1 GitLab Migration User 2018-08-25 12:53:20 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pkg-config/pkg-config/issues/11.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.