You can probably have Module::Build and such play with the PKG_CONFIG_PATH env variable to fill out where it should be. On Jan 6, 2014 10:51 AM, "Paul "LeoNerd" Evans" <leon...@leonerd.org.uk> wrote:
> So, another Alien question. > > I have two C libraries. One depends on the other. (Actually, it's more > of a one-of-many dependencies, but this way it easiest). How is best to > arrange for this to happen then? > > Outside of perl/Alien wrappings, this is a purely manual process. > Install first library (as root) so its pkg-config file is created, then > the Makefile in the second library finds this, adds cflags/ldflags, all > well and good. > > But Aliens complicate this, because of the requirement that non-root > users can install and use them. This requires the first library to get > installed somewhere in perl's @INC where the user can write. pkg-config > won't automatically look there. This is OK for the Alien layer because > the Alien/Foo.pm can know where to find the pkg-config file. But the > second C library's Makefile can't. So how is it going to find the first > one? > > I am beginning to think that this requirement that non-root users be > able to install C libraries into non-system standard places is getting > problematic. > > -- > Paul "LeoNerd" Evans > > leon...@leonerd.org.uk > ICQ# 4135350 | Registered Linux# 179460 > http://www.leonerd.org.uk/ >
