mesonbuild/meson

pkgconfig generator should automatically populate requires/requires_private from dependency() objects

Open

#2,896 opened on Jan 8, 2018

View on GitHub
 (10 comments) (0 reactions) (0 assignees)Python (4,978 stars) (1,465 forks)batch import
enhancementgeneratorsgood first issuehelp wanted

Description

Right now, people have to specify that manually, why not to convert it automatically ;)

Contributor guide

Tech stack
python
Domain
build system
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Familiarity with Meson build system internalsUnderstanding of dependency() objectsKnowledge of Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The pkgconfig generator implementation is likely in the mesonbuild module. Start by examining the current pkgconfig module (e.g., mesonbuild/modules/pkgconfig.py) and understanding how dependency() objects store link requirements. Then, review the issue comments (10 comments) to clarify exactly which fields should be auto populated and any edge cases. Consider adding logic to automatically extract required libraries from dependency objects during generation.