The job of an Alien module is to provide the external dependency to perl for configuration and use (usually for XS modules to link against).
The job of an Alien module author is to implement that process via the Alien::XXX. Maybe you could start by figuring out how you would provide Alien functionality "by hand". Now automate that. --Chris On Thu, Jan 9, 2014 at 2:25 PM, Paul "LeoNerd" Evans <leon...@leonerd.org.uk> wrote: > On Mon, 6 Jan 2014 20:02:31 -0500 > Chris Marshall <devel.chm...@gmail.com> wrote: > >> pkg-config has a standard format. I see no reason why >> the Alien::unibilium could not make a valid .pc file that >> could be used by the standard autoconf enabled builds. > > So, it seems my solution is to have Alien::unibilium's build > process write a .pc file. Simple, right? :) > > Only, not quite so, because unibilium's "make install" will already > write one. So additionally I'll have to hunt that one down and rewrite > its contents. While understanding it all. Including all those variable > expansions and anything else the format might generate. > > This is starting to sound worse... > > -- > Paul "LeoNerd" Evans > > leon...@leonerd.org.uk > ICQ# 4135350 | Registered Linux# 179460 > http://www.leonerd.org.uk/
