Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
poppler
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 612
    • Issues 612
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 40
    • Merge Requests 40
  • 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
  • poppler
  • poppler
  • Issues
  • #760

Closed
Open
Created Apr 28, 2019 by Zdenko@zdposterContributor

POPPLER_CREATE_INSTALL_PKGCONFIG (cmake/modules/PopplerMacros.cmake) does not install *.pc files

If I build poppler with MSVC (or clang with MSVC compatibility) *.pc are not installed because of condition in cmake/modules/PopplerMacros.cmake

IMO this is not correct approach:

  1. pc file has nothing to do with compiler
  2. if somebody want to limit installation of pc file, it should be related to presence of pkg_config (PKG_CONFIG_EXECUTABLE). In such case I would suggest to at least print message that pc files will not be installed.

Personally I would install pc files always as user can install pkg_config later so there is no need to reinstall poppler.

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