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
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
On Mon, 6 Jan 2014 11:12:49 -0800
Ryan Voots simcop2...@simcop2387.info wrote:
You can probably have Module::Build and such play with the
PKG_CONFIG_PATH env variable to fill out where it should be.
Hah, if only it were so simple...
The trouble with non-standard install locations is that in
Paul -
Why use pkg_config when you can simply use include_dirs and
extra_linker_flags (or their equivalent in EU::MM)? This is how I do
things with Alien::TinyCC. See the
Synopsishttps://metacpan.org/pod/Alien::TinyCC.
Or is this approach insufficient for unibilium?
David
On Mon, Jan 6, 2014
On Mon, 6 Jan 2014 16:49:54 -0500
David Mertens dcmertens.p...@gmail.com wrote:
Why use pkg_config when you can simply use include_dirs and
extra_linker_flags (or their equivalent in EU::MM)? This is how I do
things with Alien::TinyCC. See the
Synopsishttps://metacpan.org/pod/Alien::TinyCC.
Hi Paul-
I'm a bit confused by the discussion so far. Alien modules are to
provide external dependencies wrapped up for perl modules to use
and not, in general, as a way to resolve C library dependencies.
Once installed, an Alien module should provide all the information
needed to use the
On Mon, 6 Jan 2014 17:21:04 -0500
Chris Marshall devel.chm...@gmail.com wrote:
Hi Paul-
I'm a bit confused by the discussion so far. Alien modules are to
provide external dependencies wrapped up for perl modules to use
and not, in general, as a way to resolve C library dependencies.
Once
On Mon, Jan 6, 2014 at 5:32 PM, Paul LeoNerd Evans
leon...@leonerd.org.uk wrote:
On Mon, 6 Jan 2014 17:21:04 -0500
Chris Marshall devel.chm...@gmail.com wrote:
Hi Paul-
I'm a bit confused by the discussion so far. Alien modules are to
provide external dependencies wrapped up for perl
On Mon, 6 Jan 2014 17:54:56 -0500
Chris Marshall devel.chm...@gmail.com wrote:
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.
* 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
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_PATHhttp://askubuntu.com/questions/210210/pkg-config-path-environment-variable.
I had trouble
On Mon, Jan 6, 2014 at 6:43 PM, Paul LeoNerd Evans
leon...@leonerd.org.uk wrote:
On Mon, 6 Jan 2014 17:54:56 -0500
Chris Marshall devel.chm...@gmail.com wrote:
Again, Alien modules are for *perl* to access external dependencies
and not for other external dependencies to access
12 matches
Mail list logo
