On Mon, Jan 6, 2014 at 5:54 PM, Chris Marshall <devel.chm...@gmail.com> wrote: > On Mon, Jan 6, 2014 at 5:32 PM, Paul "LeoNerd" Evans > <leon...@leonerd.org.uk> wrote: >> ... >> >> This surely limits Alien wrappings to only being useful for C libraries >> that don't themselves have other C-level dependencies. >> >> Unless I have missed something - how does anyone else do this? > > I think you missed my example above where Alien::libtermkey could > be Alien::A and Alien::unibilium would be Alien::B (I think).
It looks like libtermkey depends on unibilium so the above is backwards. Otherwise the example is the same. > Again, Alien modules are for *perl* to access external dependencies > and not for other external dependencies to access eachother---you've > already given a bunch of examples of the standard pkg-config use > in builds. > > --Chris
