How to use libraries installed with a package manager in GNU/Linux
up vote
2
down vote
favorite
I installed a library(for example lzma-dev) using a package manager(for example apt-get for Debian or Ubuntu). How can I use it? Where can I find the libs and headers? How about sos(dynamic libraries)?
libraries development
edited yesterday
Rui F Ribeiro
38.6k1479128
asked Feb 13 '14 at 8:18
Jason Swartz
13117
add a comment |
up vote
2
down vote
favorite
I installed a library(for example lzma-dev) using a package manager(for example apt-get for Debian or Ubuntu). How can I use it? Where can I find the libs and headers? How about sos(dynamic libraries)?
libraries development
edited yesterday
Rui F Ribeiro
38.6k1479128
asked Feb 13 '14 at 8:18
Jason Swartz
13117
1
Essentially, any properly set-up distro will ensure that libraries installed via its package manager can be found in directories that are in the compiler's default search path. (Assuming that the compiler was likewise installed via the package manager)
– Shadur
Feb 13 '14 at 13:40
@Shadur this means I can just#include <header.h>(for example for c++ libraries) and use it right along without having to think about adding library and include paths to the porject file, right?
– Jason Swartz
Feb 13 '14 at 14:18
1
In most cases, yes, although from the looks of @slm's the files will be at/usr/include/<libname>so the include directive you'll likely need would be#include <libname/header.h>
– Shadur
Feb 13 '14 at 14:37
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I installed a library(for example lzma-dev) using a package manager(for example apt-get for Debian or Ubuntu). How can I use it? Where can I find the libs and headers? How about sos(dynamic libraries)?
libraries development
edited yesterday
Rui F Ribeiro
38.6k1479128
asked Feb 13 '14 at 8:18
Jason Swartz
13117
I installed a library(for example lzma-dev) using a package manager(for example apt-get for Debian or Ubuntu). How can I use it? Where can I find the libs and headers? How about sos(dynamic libraries)?
libraries development
libraries development
edited yesterday
Rui F Ribeiro
38.6k1479128
asked Feb 13 '14 at 8:18
Jason Swartz
13117
edited yesterday
Rui F Ribeiro
38.6k1479128
asked Feb 13 '14 at 8:18
Jason Swartz
13117
edited yesterday
Rui F Ribeiro
38.6k1479128
edited yesterday
Rui F Ribeiro
38.6k1479128
edited yesterday
Rui F Ribeiro
38.6k1479128
38.6k1479128
asked Feb 13 '14 at 8:18
Jason Swartz
13117
asked Feb 13 '14 at 8:18
Jason Swartz
13117
asked Feb 13 '14 at 8:18
Jason Swartz
13117
13117
1
Essentially, any properly set-up distro will ensure that libraries installed via its package manager can be found in directories that are in the compiler's default search path. (Assuming that the compiler was likewise installed via the package manager)
– Shadur
Feb 13 '14 at 13:40
@Shadur this means I can just#include <header.h>(for example for c++ libraries) and use it right along without having to think about adding library and include paths to the porject file, right?
– Jason Swartz
Feb 13 '14 at 14:18
1
In most cases, yes, although from the looks of @slm's the files will be at/usr/include/<libname>so the include directive you'll likely need would be#include <libname/header.h>
– Shadur
Feb 13 '14 at 14:37
add a comment |
1
Essentially, any properly set-up distro will ensure that libraries installed via its package manager can be found in directories that are in the compiler's default search path. (Assuming that the compiler was likewise installed via the package manager)
– Shadur
Feb 13 '14 at 13:40
@Shadur this means I can just#include <header.h>(for example for c++ libraries) and use it right along without having to think about adding library and include paths to the porject file, right?
– Jason Swartz
Feb 13 '14 at 14:18
1
In most cases, yes, although from the looks of @slm's the files will be at/usr/include/<libname>so the include directive you'll likely need would be#include <libname/header.h>
– Shadur
Feb 13 '14 at 14:37
1
1
Essentially, any properly set-up distro will ensure that libraries installed via its package manager can be found in directories that are in the compiler's default search path. (Assuming that the compiler was likewise installed via the package manager)
– Shadur
Feb 13 '14 at 13:40
Essentially, any properly set-up distro will ensure that libraries installed via its package manager can be found in directories that are in the compiler's default search path. (Assuming that the compiler was likewise installed via the package manager)
– Shadur
Feb 13 '14 at 13:40
@Shadur this means I can just
#include <header.h>(for example for c++ libraries) and use it right along without having to think about adding library and include paths to the porject file, right?– Jason Swartz
Feb 13 '14 at 14:18
@Shadur this means I can just
#include <header.h>(for example for c++ libraries) and use it right along without having to think about adding library and include paths to the porject file, right?– Jason Swartz
Feb 13 '14 at 14:18
1
1
In most cases, yes, although from the looks of @slm's the files will be at
/usr/include/<libname> so the include directive you'll likely need would be #include <libname/header.h>– Shadur
Feb 13 '14 at 14:37
In most cases, yes, although from the looks of @slm's the files will be at
/usr/include/<libname> so the include directive you'll likely need would be #include <libname/header.h>– Shadur
Feb 13 '14 at 14:37
add a comment |
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
Assuming the package has already been installed you can see the contents of it using dpkg -L, for list.
Example
$ dpkg -L lzma-dev
/.
/usr
/usr/include
/usr/include/lzma
/usr/include/lzma/LzHash.h
/usr/include/lzma/Types.h
/usr/include/lzma/LzmaEnc.h
/usr/include/lzma/LzFind.c
/usr/include/lzma/LzmaEnc.c
/usr/include/lzma/LzFind.h
/usr/include/lzma/LzmaDec.h
/usr/include/lzma/7zVersion.h
/usr/include/lzma/LzmaDec.c
/usr/share
/usr/share/doc
/usr/share/doc/lzma-dev
/usr/share/doc/lzma-dev/lzma.txt.gz
/usr/share/doc/lzma-dev/Methods.txt
/usr/share/doc/lzma-dev/7zC.txt.gz
/usr/share/doc/lzma-dev/changelog.Debian.gz
/usr/share/doc/lzma-dev/7zFormat.txt.gz
/usr/share/doc/lzma-dev/copyright
Packages that are named <something>-dev are typically just the C header files (.h files), this package is a bit unusual in that it includes (.c and .h files). Incidentally this is the actual source for the LZMA library.
If you want the .so files and the .h files for the LZMA library, so you can compile against it, you'll need to install the 'liblzma-dev` package.
Example
Here's the header files.
$ dpkg -L liblzma-dev | tail -15
/usr/include/lzma/version.h
/usr/include/lzma/hardware.h
/usr/include/lzma/index.h
/usr/include/lzma/index_hash.h
/usr/include/lzma/block.h
/usr/include/lzma/delta.h
/usr/include/lzma/check.h
/usr/include/lzma/filter.h
/usr/include/lzma/bcj.h
/usr/include/lzma/base.h
/usr/share/doc/liblzma-dev/NEWS.gz
/usr/share/doc/liblzma-dev/AUTHORS
/usr/share/doc/liblzma-dev/changelog.Debian.gz
/usr/share/doc/liblzma-dev/THANKS
/usr/lib/x86_64-linux-gnu/liblzma.so
As well as the actual .so library:
$ dpkg -L liblzma5 | tail -4
/lib
/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu/liblzma.so.5.0.0
/lib/x86_64-linux-gnu/liblzma.so.5
answered Feb 13 '14 at 9:02
slm♦
246k66507673
"and the .c and .h files for the LZMA library". The.cfiles are not packaged. They're source. Also,.sofiles are not part of a dev library, which just contain header files. The/usr/lib/x86_64-linux-gnu/liblzma.sohere is a symbolic link. It points to a file in the library packageliblzma5.
– Faheem Mitha
Feb 13 '14 at 18:31
@FaheemMitha - take a look at the contents of lzma-dev, it does contain .c files.
– slm♦
Feb 13 '14 at 18:39
@FaheemMitha - cleaned it up but this is a bit of a confusing example.
– slm♦
Feb 13 '14 at 18:45
@FaheemMitha - 12.10, lzma-dev: 9.22-2ubuntu2
– slm♦
Feb 13 '14 at 22:50
add a comment |
up vote
1
down vote
dpkg -L lzma-dev
list all the files installed with apt-get for lzma-dev
answered Feb 13 '14 at 8:21
Timo
4,7251726
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f114999%2fhow-to-use-libraries-installed-with-a-package-manager-in-gnu-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Assuming the package has already been installed you can see the contents of it using dpkg -L, for list.
Example
$ dpkg -L lzma-dev
/.
/usr
/usr/include
/usr/include/lzma
/usr/include/lzma/LzHash.h
/usr/include/lzma/Types.h
/usr/include/lzma/LzmaEnc.h
/usr/include/lzma/LzFind.c
/usr/include/lzma/LzmaEnc.c
/usr/include/lzma/LzFind.h
/usr/include/lzma/LzmaDec.h
/usr/include/lzma/7zVersion.h
/usr/include/lzma/LzmaDec.c
/usr/share
/usr/share/doc
/usr/share/doc/lzma-dev
/usr/share/doc/lzma-dev/lzma.txt.gz
/usr/share/doc/lzma-dev/Methods.txt
/usr/share/doc/lzma-dev/7zC.txt.gz
/usr/share/doc/lzma-dev/changelog.Debian.gz
/usr/share/doc/lzma-dev/7zFormat.txt.gz
/usr/share/doc/lzma-dev/copyright
Packages that are named <something>-dev are typically just the C header files (.h files), this package is a bit unusual in that it includes (.c and .h files). Incidentally this is the actual source for the LZMA library.
If you want the .so files and the .h files for the LZMA library, so you can compile against it, you'll need to install the 'liblzma-dev` package.
Example
Here's the header files.
$ dpkg -L liblzma-dev | tail -15
/usr/include/lzma/version.h
/usr/include/lzma/hardware.h
/usr/include/lzma/index.h
/usr/include/lzma/index_hash.h
/usr/include/lzma/block.h
/usr/include/lzma/delta.h
/usr/include/lzma/check.h
/usr/include/lzma/filter.h
/usr/include/lzma/bcj.h
/usr/include/lzma/base.h
/usr/share/doc/liblzma-dev/NEWS.gz
/usr/share/doc/liblzma-dev/AUTHORS
/usr/share/doc/liblzma-dev/changelog.Debian.gz
/usr/share/doc/liblzma-dev/THANKS
/usr/lib/x86_64-linux-gnu/liblzma.so
As well as the actual .so library:
$ dpkg -L liblzma5 | tail -4
/lib
/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu/liblzma.so.5.0.0
/lib/x86_64-linux-gnu/liblzma.so.5
answered Feb 13 '14 at 9:02
slm♦
246k66507673
"and the .c and .h files for the LZMA library". The.cfiles are not packaged. They're source. Also,.sofiles are not part of a dev library, which just contain header files. The/usr/lib/x86_64-linux-gnu/liblzma.sohere is a symbolic link. It points to a file in the library packageliblzma5.
– Faheem Mitha
Feb 13 '14 at 18:31
@FaheemMitha - take a look at the contents of lzma-dev, it does contain .c files.
– slm♦
Feb 13 '14 at 18:39
@FaheemMitha - cleaned it up but this is a bit of a confusing example.
– slm♦
Feb 13 '14 at 18:45
@FaheemMitha - 12.10, lzma-dev: 9.22-2ubuntu2
– slm♦
Feb 13 '14 at 22:50
add a comment |
up vote
3
down vote
accepted
Assuming the package has already been installed you can see the contents of it using dpkg -L, for list.
Example
$ dpkg -L lzma-dev
/.
/usr
/usr/include
/usr/include/lzma
/usr/include/lzma/LzHash.h
/usr/include/lzma/Types.h
/usr/include/lzma/LzmaEnc.h
/usr/include/lzma/LzFind.c
/usr/include/lzma/LzmaEnc.c
/usr/include/lzma/LzFind.h
/usr/include/lzma/LzmaDec.h
/usr/include/lzma/7zVersion.h
/usr/include/lzma/LzmaDec.c
/usr/share
/usr/share/doc
/usr/share/doc/lzma-dev
/usr/share/doc/lzma-dev/lzma.txt.gz
/usr/share/doc/lzma-dev/Methods.txt
/usr/share/doc/lzma-dev/7zC.txt.gz
/usr/share/doc/lzma-dev/changelog.Debian.gz
/usr/share/doc/lzma-dev/7zFormat.txt.gz
/usr/share/doc/lzma-dev/copyright
Packages that are named <something>-dev are typically just the C header files (.h files), this package is a bit unusual in that it includes (.c and .h files). Incidentally this is the actual source for the LZMA library.
If you want the .so files and the .h files for the LZMA library, so you can compile against it, you'll need to install the 'liblzma-dev` package.
Example
Here's the header files.
$ dpkg -L liblzma-dev | tail -15
/usr/include/lzma/version.h
/usr/include/lzma/hardware.h
/usr/include/lzma/index.h
/usr/include/lzma/index_hash.h
/usr/include/lzma/block.h
/usr/include/lzma/delta.h
/usr/include/lzma/check.h
/usr/include/lzma/filter.h
/usr/include/lzma/bcj.h
/usr/include/lzma/base.h
/usr/share/doc/liblzma-dev/NEWS.gz
/usr/share/doc/liblzma-dev/AUTHORS
/usr/share/doc/liblzma-dev/changelog.Debian.gz
/usr/share/doc/liblzma-dev/THANKS
/usr/lib/x86_64-linux-gnu/liblzma.so
As well as the actual .so library:
$ dpkg -L liblzma5 | tail -4
/lib
/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu/liblzma.so.5.0.0
/lib/x86_64-linux-gnu/liblzma.so.5
answered Feb 13 '14 at 9:02
slm♦
246k66507673
"and the .c and .h files for the LZMA library". The.cfiles are not packaged. They're source. Also,.sofiles are not part of a dev library, which just contain header files. The/usr/lib/x86_64-linux-gnu/liblzma.sohere is a symbolic link. It points to a file in the library packageliblzma5.
– Faheem Mitha
Feb 13 '14 at 18:31
@FaheemMitha - take a look at the contents of lzma-dev, it does contain .c files.
– slm♦
Feb 13 '14 at 18:39
@FaheemMitha - cleaned it up but this is a bit of a confusing example.
– slm♦
Feb 13 '14 at 18:45
@FaheemMitha - 12.10, lzma-dev: 9.22-2ubuntu2
– slm♦
Feb 13 '14 at 22:50
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Assuming the package has already been installed you can see the contents of it using dpkg -L, for list.
Example
$ dpkg -L lzma-dev
/.
/usr
/usr/include
/usr/include/lzma
/usr/include/lzma/LzHash.h
/usr/include/lzma/Types.h
/usr/include/lzma/LzmaEnc.h
/usr/include/lzma/LzFind.c
/usr/include/lzma/LzmaEnc.c
/usr/include/lzma/LzFind.h
/usr/include/lzma/LzmaDec.h
/usr/include/lzma/7zVersion.h
/usr/include/lzma/LzmaDec.c
/usr/share
/usr/share/doc
/usr/share/doc/lzma-dev
/usr/share/doc/lzma-dev/lzma.txt.gz
/usr/share/doc/lzma-dev/Methods.txt
/usr/share/doc/lzma-dev/7zC.txt.gz
/usr/share/doc/lzma-dev/changelog.Debian.gz
/usr/share/doc/lzma-dev/7zFormat.txt.gz
/usr/share/doc/lzma-dev/copyright
Packages that are named <something>-dev are typically just the C header files (.h files), this package is a bit unusual in that it includes (.c and .h files). Incidentally this is the actual source for the LZMA library.
If you want the .so files and the .h files for the LZMA library, so you can compile against it, you'll need to install the 'liblzma-dev` package.
Example
Here's the header files.
$ dpkg -L liblzma-dev | tail -15
/usr/include/lzma/version.h
/usr/include/lzma/hardware.h
/usr/include/lzma/index.h
/usr/include/lzma/index_hash.h
/usr/include/lzma/block.h
/usr/include/lzma/delta.h
/usr/include/lzma/check.h
/usr/include/lzma/filter.h
/usr/include/lzma/bcj.h
/usr/include/lzma/base.h
/usr/share/doc/liblzma-dev/NEWS.gz
/usr/share/doc/liblzma-dev/AUTHORS
/usr/share/doc/liblzma-dev/changelog.Debian.gz
/usr/share/doc/liblzma-dev/THANKS
/usr/lib/x86_64-linux-gnu/liblzma.so
As well as the actual .so library:
$ dpkg -L liblzma5 | tail -4
/lib
/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu/liblzma.so.5.0.0
/lib/x86_64-linux-gnu/liblzma.so.5
answered Feb 13 '14 at 9:02
slm♦
246k66507673
Assuming the package has already been installed you can see the contents of it using dpkg -L, for list.
Example
$ dpkg -L lzma-dev
/.
/usr
/usr/include
/usr/include/lzma
/usr/include/lzma/LzHash.h
/usr/include/lzma/Types.h
/usr/include/lzma/LzmaEnc.h
/usr/include/lzma/LzFind.c
/usr/include/lzma/LzmaEnc.c
/usr/include/lzma/LzFind.h
/usr/include/lzma/LzmaDec.h
/usr/include/lzma/7zVersion.h
/usr/include/lzma/LzmaDec.c
/usr/share
/usr/share/doc
/usr/share/doc/lzma-dev
/usr/share/doc/lzma-dev/lzma.txt.gz
/usr/share/doc/lzma-dev/Methods.txt
/usr/share/doc/lzma-dev/7zC.txt.gz
/usr/share/doc/lzma-dev/changelog.Debian.gz
/usr/share/doc/lzma-dev/7zFormat.txt.gz
/usr/share/doc/lzma-dev/copyright
Packages that are named <something>-dev are typically just the C header files (.h files), this package is a bit unusual in that it includes (.c and .h files). Incidentally this is the actual source for the LZMA library.
If you want the .so files and the .h files for the LZMA library, so you can compile against it, you'll need to install the 'liblzma-dev` package.
Example
Here's the header files.
$ dpkg -L liblzma-dev | tail -15
/usr/include/lzma/version.h
/usr/include/lzma/hardware.h
/usr/include/lzma/index.h
/usr/include/lzma/index_hash.h
/usr/include/lzma/block.h
/usr/include/lzma/delta.h
/usr/include/lzma/check.h
/usr/include/lzma/filter.h
/usr/include/lzma/bcj.h
/usr/include/lzma/base.h
/usr/share/doc/liblzma-dev/NEWS.gz
/usr/share/doc/liblzma-dev/AUTHORS
/usr/share/doc/liblzma-dev/changelog.Debian.gz
/usr/share/doc/liblzma-dev/THANKS
/usr/lib/x86_64-linux-gnu/liblzma.so
As well as the actual .so library:
$ dpkg -L liblzma5 | tail -4
/lib
/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu/liblzma.so.5.0.0
/lib/x86_64-linux-gnu/liblzma.so.5
answered Feb 13 '14 at 9:02
slm♦
246k66507673
edited Feb 13 '14 at 18:44
answered Feb 13 '14 at 9:02
slm♦
246k66507673
answered Feb 13 '14 at 9:02
slm♦
246k66507673
answered Feb 13 '14 at 9:02
slm♦
246k66507673
246k66507673
"and the .c and .h files for the LZMA library". The.cfiles are not packaged. They're source. Also,.sofiles are not part of a dev library, which just contain header files. The/usr/lib/x86_64-linux-gnu/liblzma.sohere is a symbolic link. It points to a file in the library packageliblzma5.
– Faheem Mitha
Feb 13 '14 at 18:31
@FaheemMitha - take a look at the contents of lzma-dev, it does contain .c files.
– slm♦
Feb 13 '14 at 18:39
@FaheemMitha - cleaned it up but this is a bit of a confusing example.
– slm♦
Feb 13 '14 at 18:45
@FaheemMitha - 12.10, lzma-dev: 9.22-2ubuntu2
– slm♦
Feb 13 '14 at 22:50
add a comment |
"and the .c and .h files for the LZMA library". The.cfiles are not packaged. They're source. Also,.sofiles are not part of a dev library, which just contain header files. The/usr/lib/x86_64-linux-gnu/liblzma.sohere is a symbolic link. It points to a file in the library packageliblzma5.
– Faheem Mitha
Feb 13 '14 at 18:31
@FaheemMitha - take a look at the contents of lzma-dev, it does contain .c files.
– slm♦
Feb 13 '14 at 18:39
@FaheemMitha - cleaned it up but this is a bit of a confusing example.
– slm♦
Feb 13 '14 at 18:45
@FaheemMitha - 12.10, lzma-dev: 9.22-2ubuntu2
– slm♦
Feb 13 '14 at 22:50
"and the .c and .h files for the LZMA library". The
.c files are not packaged. They're source. Also, .so files are not part of a dev library, which just contain header files. The /usr/lib/x86_64-linux-gnu/liblzma.so here is a symbolic link. It points to a file in the library package liblzma5.– Faheem Mitha
Feb 13 '14 at 18:31
"and the .c and .h files for the LZMA library". The
.c files are not packaged. They're source. Also, .so files are not part of a dev library, which just contain header files. The /usr/lib/x86_64-linux-gnu/liblzma.so here is a symbolic link. It points to a file in the library package liblzma5.– Faheem Mitha
Feb 13 '14 at 18:31
@FaheemMitha - take a look at the contents of lzma-dev, it does contain .c files.
– slm♦
Feb 13 '14 at 18:39
@FaheemMitha - take a look at the contents of lzma-dev, it does contain .c files.
– slm♦
Feb 13 '14 at 18:39
@FaheemMitha - cleaned it up but this is a bit of a confusing example.
– slm♦
Feb 13 '14 at 18:45
@FaheemMitha - cleaned it up but this is a bit of a confusing example.
– slm♦
Feb 13 '14 at 18:45
@FaheemMitha - 12.10, lzma-dev: 9.22-2ubuntu2
– slm♦
Feb 13 '14 at 22:50
@FaheemMitha - 12.10, lzma-dev: 9.22-2ubuntu2
– slm♦
Feb 13 '14 at 22:50
add a comment |
up vote
1
down vote
dpkg -L lzma-dev
list all the files installed with apt-get for lzma-dev
answered Feb 13 '14 at 8:21
Timo
4,7251726
add a comment |
up vote
1
down vote
dpkg -L lzma-dev
list all the files installed with apt-get for lzma-dev
answered Feb 13 '14 at 8:21
Timo
4,7251726
add a comment |
up vote
1
down vote
up vote
1
down vote
dpkg -L lzma-dev
list all the files installed with apt-get for lzma-dev
answered Feb 13 '14 at 8:21
Timo
4,7251726
dpkg -L lzma-dev
list all the files installed with apt-get for lzma-dev
answered Feb 13 '14 at 8:21
Timo
4,7251726
answered Feb 13 '14 at 8:21
Timo
4,7251726
answered Feb 13 '14 at 8:21
Timo
4,7251726
answered Feb 13 '14 at 8:21
Timo
4,7251726
4,7251726
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f114999%2fhow-to-use-libraries-installed-with-a-package-manager-in-gnu-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Essentially, any properly set-up distro will ensure that libraries installed via its package manager can be found in directories that are in the compiler's default search path. (Assuming that the compiler was likewise installed via the package manager)
– Shadur
Feb 13 '14 at 13:40
@Shadur this means I can just
#include <header.h>(for example for c++ libraries) and use it right along without having to think about adding library and include paths to the porject file, right?– Jason Swartz
Feb 13 '14 at 14:18
1
In most cases, yes, although from the looks of @slm's the files will be at
/usr/include/<libname>so the include directive you'll likely need would be#include <libname/header.h>– Shadur
Feb 13 '14 at 14:37