RFC: parrot_config over pkg-config for dynext build configuration

Gerd Pokorra gp at zimt.uni-siegen.de
Wed Nov 10 15:12:43 UTC 2010

I think there is no need to make mention of "pkg-config" in the
documentation. I believe it is better to have an example of
"parrot_config" there. But I think not to note "pkg-config" in the PPD
is enough. Some linux distributions like to have the file "parrot.pc".

-- Gerd

Am Mittwoch, den 10.11.2010, 05:26 +0100 schrieb Peter Lobsinger:
> PDD30 and pkg-config don't work well together leading to the problems
> described in TT #1842. In my opinion, the purpose of pkg-config
> doesn't really agree with the goal of multiple installed versions.
> Further, it is not likely to be installed on many systems we are
> targeting.
> parrot_config should contain any parrot configuration information,
> including whatever is contained in parrot.pc. It is also already the
> recommended way for languages to build themselves for a particular
> parrot (pdd30). Rakudo already uses parrot_config for this purpose.
> Therefore I wish to deprecate parrot.pc and rewrite the appropriate
> sections of docs/embed.pod to use parrot_config in stead.
> Comments?
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev

More information about the parrot-dev mailing list