pkgconfig.generate() produces different files the second time
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.6k
- Forks
- 1.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 33
Description
```
project('shared library test', 'c')
lib = shared_library('mylib')
pkg = import('pkgconfig')
pkg.generate(lib, filebase: 'foo')
pkg.generate(lib, filebase: 'bar')
```
Results in two different files:
```diff
$ diff -Nur foo.pc bar.pc
--- foo.pc 2019-06-13 23:24:33.150752000 +0200
+++ bar.pc 2019-06-13 23:24:33.150752000 +0200
@@ -5,5 +5,5 @@
Name: mylib
Description: shared library test: mylib
Version: undefined
-Libs: -L${libdir} -lmylib
+Requires: foo
Cflags: -I${includedir}
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the two pkgconfig.generate() calls shown in the report and compare foo.pc with bar.pc. Trace the pkgconfig.generate entry point and its handling of repeated generation; done means equivalent inputs produce consistent, correct package files rather than changing the second output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100