Talk:pkg-config

This is the talk page for discussing improvements to the Pkg-config article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Computing: Software / Free and open-source software Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).
	This article is supported by Free and open-source software (assessed as Low-importance).

Untitled

There's some noise about pkg-config `concept' beeing broken see this post and this one from Wine's project leader.

I didn't find details over this brokeness statement. Potorange (talk) 14:17, 8 January 2009 (UTC)[reply]

The first link is not relevant (the cause in the erroneously specification of a library or of its usage), the second link does not give any rational. --Hibou57 (talk) 04:12, 15 August 2014 (UTC)[reply]

A standard or a software?

To my understanding, `pkg-config` is more a standard than a software, and Freedesktop is indeed about standards, although it's doing the same error (to my eyes) as Wikipedia, referring to it as a software instead of as a standard. If `pkg-config` is not at least also a standard and just software, then how its behaviour specified? Another point of view, is that if I'm not wrong, there use to be applications like Code::Blocks, reading and interpreting `*.pc` files without relying on the legacy `pkg-config` application. --Hibou57 (talk) 04:18, 15 August 2014 (UTC)[reply]

The new kid on the block is `pkgconf` which can be used as a drop-in replacement for `pkg-config` using a symlink. It also provides a library, `libpkgconf` that provides access to most of `pkgconf`s functionality. Ebichu63 (talk) 10:04, 12 February 2021 (UTC)[reply]

Using pkg-config on platforms other than Linux

I am by no means an expert on this topic, but I was doing some related research I found a comment saying something to the effect of "gcc test.c `pkg-config --cflags --libs glib-2.0`" doesn't work on some non-linux machines, and you should use the format gcc `pkg-config --cflags glib-2.0` test.c `pkg-config --libs glib-2.0` instead".

I'm not sure if this is right in all cases, but it might be something to mention. Link^[1] for reference.

MajorTechBoy (talk) 04:32, 6 September 2018 (UTC)[reply]

References

^ https://stackoverflow.com/questions/1146010/why-cant-i-build-a-hello-world-for-glib

History

It would be nice to see a bit more about the history. I like pkg-config and I have noticed that it actually solves problems that "--version" invocations do not solve (e. g. dissimilar results again, based on different authors). So I wondered how to suggest to more people to add .pc files, and for this it would be interesting to see the history. I see that it was released in 2000 but I don't know more than that. Would be nice if wikipedia could gather more facts here, as an intro to it. 2A02:8388:1641:8380:3AD5:47FF:FE18:CC7F (talk) 11:13, 28 August 2020 (UTC)[reply]

[1] ttps://stackoverflow.com/questions/1146010/why-cant-i-build-a-hello-world-for-glib

[1]