Ticket #1842 (closed bug: fixed)
Linking against libparrot not as documented
Reported by: | plobsing | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 2.10 |
Component: | embed/extend | Version: | 2.10.0 |
Severity: | high | Keywords: | |
Cc: | Language: | ||
Patch status: | Platform: |
Description
How do you link against libparrot? Easy - use pkg-config like docs/embed.pod tells you.
Except NONE of those commands work!
A little experimenting with pkg-config or a casual glance at the pkg-config source would let anyone know that it does not recurse into subdirectories, so pkgconfig/parrot/2.9.1/parrot.pc is Less Than Useful.
This is a blocker for anyone who is trying to link against libparrot The Right Way.
For the full details of why this happened, check out a previous attempt to remedy this (as well as other issues): TT #735.
If we want to be able to support multiple installed versions of parrot using the current install file policy, pkg-config is not going to cut it. I suggest we abandon pkg-config as a solution, and move to what rakudo is doing: pull everything from parrot_config.