Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
pkg-config
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 56
    • Issues 56
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 7
    • Merge Requests 7
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pkg-config
  • pkg-config
  • Issues
  • #11

Closed
Open
Opened Feb 15, 2018 by Bugzilla Migration User@bugzilla-migration

windows: libdir variant for static linking

Submitted by Clemens Buchacher

Assigned to pkg..@..op.org

Link to original bug (#105112)

Description

Hi,

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?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: pkg-config/pkg-config#11