Yes, exactly what Aristotle says. You need to add Alien::unibilium to your configure_requires, and your Alien::unibilium module needs to have either a method or an import function that sets the PKG_CONFIG_PATH<http://askubuntu.com/questions/210210/pkg-config-path-environment-variable>. I had trouble getting this approach to work with MakeMaker because MakeMaker doesn't invoke my Alien module except at the moment I run Makefile.PL. This is why I use Module::Build.
David On Mon, Jan 6, 2014 at 7:22 PM, Aristotle Pagaltzis <pagalt...@gmx.de>wrote: > * Paul "LeoNerd" Evans <leon...@leonerd.org.uk> [2014-01-06 23:35]: > > Now consider Alien. > > > > Alien::unibilium installs unibilium into the only place it knows > > how - namely, somewhere in Perl's @INC dir. > > > > At this point, how does the C library "libtermkey"'s Makefile, > > manage to find unibilium, to link against it? > > > > The pkg-config that libtermkey's Makefile invokes cannot itself find > > the unibilium.pc file because it's hidden in Perl's @INC dir. > > > > I currently can't see how Alien::libtermkey /can/ provide a totally > > hassle-free self-contained "just do it" installation of libtermkey and > > its own C-level dependencies, because of this fact. > > You need to configure_requires Alien::unibilium and the module must > provide API to query its install location such that the Makefile.PL or > Build.PL from Alien::libtermkey can set things up as necessary. (Or > maybe Alien::unibilium would provide API to tweak the environment to > taste. Not sure which one would be the less leaky abstraction.) > > -- > Aristotle Pagaltzis // <http://plasmasturm.org/> > -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." -- Brian Kernighan
