pkgconfig is the defacto standard to find components. Instead of
opting-in to depending on pkgconfig via USES=pkgconfig, this switches
the behaviour to be opt-out.
If a port does not want pkgconfig, it now needs to define
WITHOUT_PKGCONFIG=yes
| Unknown Object (File) | |
| Sun, Nov 23, 1:00 AM |
| Unknown Object (File) | |
| Thu, Nov 13, 6:52 AM |
| Unknown Object (File) | |
| Mon, Nov 3, 4:00 AM |
| Unknown Object (File) | |
| Tue, Oct 28, 2:17 PM |
| Unknown Object (File) | |
| Oct 20 2025, 1:26 AM |
| Unknown Object (File) | |
| Oct 20 2025, 1:25 AM |
| Unknown Object (File) | |
| Oct 19 2025, 11:23 AM |
| Unknown Object (File) | |
| Oct 18 2025, 9:44 PM |
pkgconfig is the defacto standard to find components. Instead of
opting-in to depending on pkgconfig via USES=pkgconfig, this switches
the behaviour to be opt-out.
If a port does not want pkgconfig, it now needs to define
WITHOUT_PKGCONFIG=yes
| No Lint Coverage |
| No Test Coverage |
| Buildable 47267 | |
| Build 44154: arc lint + arc unit |
| Mk/Features/pkgconfig.mk | ||
|---|---|---|
| 10 | ^ check probably should be on !empty()? | |
| Mk/Uses/qt-dist.mk | ||
|---|---|---|
| 156 | Why was qmake excluded, for efficiency? | |
| Mk/Uses/qt-dist.mk | ||
|---|---|---|
| 156 | I think that information is lot to time :) -- I have no clue why it was done that way (if there was a good reason, the exp-run should hopefully show it). | |
As discussed with @bapt, I'll try to look into an other way to make pc-support better.