Re: pkg-config difference when run in pkgsrc vs normal run?

[Taylor R Campbell <campbell+netbsd-tech-pkg%mumble.net@localhost>]

> Date: Sat, 6 Jul 2024 18:39:03 +0300
> From: Andrew Randrianasulu <randrianasulu%gmail.com@localhost>
> 
> I see it uses file mk/tools/pkg-config.mk and this file
> uses TOOLS_SCRIPT_DFLT define and this lives somewhere in ./mk/tools/
> create.mk or ./mk/tools/bsd.tools.mk but there I am a bit lost.

Normally, you don't need to touch any of that.

What you need to do is:

1. USE_TOOLS+= pkg-config

2. For each library you depend on, say devel/libfoo:
   .include "../../devel/libfoo/buildlink3.mk"

Then pkgsrc will arrange to expose those libraries -- and only those
libraries -- through pkg-config.

How it works under the hood of mk/tools/pkg-config.mk isn't important
for pkgsrc package makefiles.  Your makefile just has to correctly
declare what the dependencies are.


I took a quick skim at your makefile from message-id
<CA+rFky4b+V6QAcgL=ZBPLSNEN3ubrnEGDK+2BqMOZ3gCwbDWGQ%mail.gmail.com@localhost>,
and it looks like:

(a) you have used BUILD_DEPENDS where you need to use USE_TOOLS or
TOOL_DEPENDS (USE_TOOLS for bash, probably TOOL_DEPENDS for nasm,
yasm, and mjpegtools);

(b) you have used DEPENDS where you need to use buildlink3; and

(c) you seem to have invented a new variable RUN_DEPENDS where I think
you meant to use DEPENDS.

If you simply use DEPENDS for libraries, all the libraries you're
looking for in pkg-config will be (deliberately) concealed from the
build.