kripkenstein
February 9th, 2008, 10:02 AM
Maybe this is a trivial question.
I know that to compile my own programs with some library, I need to install the -dev package for that library. That brings in the .h files into the appropriate /include directory, and so forth.
Now, say I get the library in tarball form, which I just did for gobject-introspection (http://svn.gnome.org/viewvc/gobject-introspection/trunk/) (seems interesting, thought I'd check it out). make and make install installs just the binary .so files, etc., it doesn't install the .h files anywhere. So I have in a sense the binary part of the library, but not the -dev part.
How do I get the -dev part of it? Is there some standard way during the make/make install process in which I can tell a package to install its .h files into /include? (I can see the .h files inside gobject-introspection, they just don't get installed anywhere) Or are there separate tarballs for the -dev versions?
I know that to compile my own programs with some library, I need to install the -dev package for that library. That brings in the .h files into the appropriate /include directory, and so forth.
Now, say I get the library in tarball form, which I just did for gobject-introspection (http://svn.gnome.org/viewvc/gobject-introspection/trunk/) (seems interesting, thought I'd check it out). make and make install installs just the binary .so files, etc., it doesn't install the .h files anywhere. So I have in a sense the binary part of the library, but not the -dev part.
How do I get the -dev part of it? Is there some standard way during the make/make install process in which I can tell a package to install its .h files into /include? (I can see the .h files inside gobject-introspection, they just don't get installed anywhere) Or are there separate tarballs for the -dev versions?