Issue 2184 in v8: pkg-config file

[codesite...@google.com]

Status: New
Owner: ----

New issue 2184 by slavek.k...@gmail.com: pkg-config file
http://code.google.com/p/v8/issues/detail?id=2184

Hi,
have you thought of providing a pkg-config file? It's pretty hard to link
against libv8 when I'm not sure where it is installed (generally) and I
can't get the paths by standard means (= pkg-config file) on Linux.

Thanks for considering this.

[codesite...@google.com]

Updates:
Status: Invalid
Labels: Type-FeatureRequest

Comment #1 on issue 2184 by sven...@chromium.org: pkg-config file
http://code.google.com/p/v8/issues/detail?id=2184

While we understand the need for easy integration of v8 into other
projects, pkg-config support is out of scope for the v8 project itself: The
exact details of a corresponding *.pc file are only known to the packager
of v8: Where are the resulting libraries finally installed? Where should
one put the *.pc file itself? etc. Consequently, pkg-config support for v8
has to be done by Ubuntu, openSUSE, Debian, <insert you favorite distro
here> in their .deb/.spec/... files.

[codesite...@google.com]

Comment #2 on issue 2184 by slavek.k...@gmail.com: pkg-config file
http://code.google.com/p/v8/issues/detail?id=2184

It is common that the paths are derived from configure parameters etc. Note
that most libraries provide the pkg-config files for use on Unix-like
systems. See [1] or [2] for examples how the relocatibility and other
features in pkg-config can be achieved.

[1] http://www.linuxfromscratch.org/blfs/view/6.3/general/pkgconfig.html
[2] http://people.freedesktop.org/~dbn/pkg-config-guide.html#writing

[codesite...@google.com]

Comment #3 on issue 2184 by sven...@chromium.org: pkg-config file
http://code.google.com/p/v8/issues/detail?id=2184

v8 doesn't have configure or something similar, and the generated Makefiles
don't even have an install target, so all this stuff has to be done outside
of v8. What packagers probably do is using our Makefile to build the v8
libraries (shared and/or static) and copy these libs plus the include files
somewhere suitable for packaging. Note that the last step is *outside* of
v8's build system, so there is not much we could put into a *.pc file.

I would suggest that you file a feature request for the distro you are
using.

[codesite...@google.com]

Comment #4 on issue 2184 by serkank...@gmail.com: pkg-config file
http://code.google.com/p/v8/issues/detail?id=2184

I would think this needs to be reopened. It's never the distros that should
provide this but upstream with a proper build system.

[codesite...@google.com]

Comment #5 on issue 2184 by anatol.p...@gmail.com: pkg-config file
http://code.google.com/p/v8/issues/detail?id=2184

Is there any distro that added the v8.pc file? I need one for Linux Arch. I
would like to avoid reinventing it if it is already present.

But ideally if V8 had it in the repo. And I agree with comment #4 above.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[codesite...@google.com]

Comment #6 on issue 2184 by anatol.p...@gmail.com: pkg-config file
http://code.google.com/p/v8/issues/detail?id=2184

Answering to myself in comment #5

Here is a v8.pc file for Arch package
https://github.com/anatol/archpackages/blob/master/v8/v8.pc . Distro
maintainers please feel free to reuse/improve it. Upstream developers feel
free to add it to your repository.