On Tue, Jan 10, 2006 at 01:06:29AM +0000, Nick Glencross wrote:
> 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}.

Great.  There is another bug to change the interpolation syntax to @foo@
to avoid just this issue.  Since you've already added the escape
mechanism so lets leave it in place but consider it temporary.

As a side note, Parrot::Configure::Step is only partially tested and I'm
rather nervous about messing with it until it has better test coverage.

> 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.

Seems reasonable.  That's what I with my autotool packages too.

> 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.

Another install type/class will have to be added.  I'll take care of
this when I get home this evening.  Lets leave the bug open until I've
gotten the install working.

Cheers,

-J

--

Attachment: pgpvupY0RiR23.pgp
Description: PGP signature

Reply via email to