Joshua Hoblitt (via RT) wrote:
Parrot should support pkgconfig by installing a pc data file. It should
probably be named parrot.pc.
Ok, I can do this. I've had an initial stab at it, and one thing that
I've had to do is provide a quoting mechanism into the configuration
file substitution because pkgconfig too uses ${name} for other purpose.
I've going to suggest ${{name}} as something which will be replaced
literally by ${name}.
I think that most projects leave the .pc in the top-level directory; I
don't think that we have anywhere better at the moment.
The file isn't yet installed because I don't know how to update the
MANIFEST.generated file to place it in .../lib/pkgconfig. Any help would
be great.
r11032 places parrot.pc into the build directory ready for installation.
Nick
