8 Apr
2003
8 Apr
'03
4:01 a.m.
I'm trying John Hall's book Programming Linux Games, which recommends
using libsndfile to load sound files. Unfortunately, the API has changed
since the book as written, and I can't seem to get projects to compile
with it now. There don't appear to be any instructions on the library's
homepage about linking.
Hall just says to compile the project with the -lsndfile flag. This
doesn't seem to work now - the resulting project doesn't link the object
in. The library does seem to be correctly installed
I found a message from the library's author
http://www.eca.cx/lad/2002/Mar/0311.html
which says to link the program with
gcc `sndfile-config --libs` file1.o file2.o -o program.
I don't seem to have the sndfile-config utility, which was suppoed to
get installed along with the library.
Running ./configure created makefiles in some of the subfolders in the
installation folder. I'm mainly interested in the examples folder, but I
get errors when I try to compile them with the makefile, assuming this
is what I am supposed to do.
I'd appreciate any advice.
Rohan Parkes
Melbourne
Australia
8 Apr
8 Apr
6:28 a.m.
On 08 Apr 2003 15:51:11 +1000
Rohan Parkes <rparkes(a)email.com> wrote:
gcc `sndfile-config --libs` file1.o file2.o -o program.
Thats for the old version. Nowadays (in fact for the last 15 months) you
do:
gcc `pkg-config --libs sndfile` file1.o file2.o -o program
Similarly, for compiling a C file to an object:
gcc `pkg-config --cflags sndfile` -c file.c
pkg-config is now the standard way of doing things like this.
Erik (the author :-))
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
"It's far too easy to make fun of Microsoft products, but it takes a
real man to make them work, and a god to make them do anything useful"
-- Anonymous
9 Apr
9 Apr
1:19 p.m.
Thanks for your reply, Erik.
I see now that there is some info about using pkg-config in the
documentation, but I hadn't understood its significance, being fairly
new to Linux development.
What I have is a simple test app that just opens an audio file and
prints out the properties.
I'm compiling it with
gcc test.c -o test `pkg-config --cflags --libs sndfile`
But I always get the result
./test: error while loading shared libraries: libsndfile.so.1: cannot
open shared object file: No such file or directory.
The headers and libraries referenced by pkg-config all seem to be in the
right place.
I'm presumably doing something wrong, but can't see what it is.
Rohan Parkes
Melbourne
Australia
On Tue, 2003-04-08 at 18:18, Erik de Castro Lopo wrote:
On 08 Apr 2003 15:51:11 +1000
Rohan Parkes <rparkes(a)email.com> wrote:
gcc `sndfile-config --libs` file1.o file2.o -o program.
Thats for the old version. Nowadays (in fact for the last 15 months) you
do:
gcc `pkg-config --libs sndfile` file1.o file2.o -o program
Similarly, for compiling a C file to an object:
gcc `pkg-config --cflags sndfile` -c file.c
pkg-config is now the standard way of doing things like this.
Erik (the author :-))
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
"It's far too easy to make fun of Microsoft products, but it takes a
real man to make them work, and a god to make them do anything useful"
-- Anonymous 
1:45 p.m.
Thanks for your reply, Erik.
I see now that there is some info about using pkg-config in the
documentation, but I hadn't understood its significance, being fairly
new to Linux development.
What I have is a simple test app that just opens an audio file and
prints out the properties.
I'm compiling it with
gcc test.c -o test `pkg-config --cflags --libs sndfile`
But I always get the result
./test: error while loading shared libraries: libsndfile.so.1: cannot
open shared object file: No such file or directory.
The headers and libraries referenced by pkg-config all seem to be in the
right place.
as it would have indicated during the install of libsndfile, you need
to either:
set LD_LIBRARY_PATH to include wherever the library is located OR
edit /etc/ld.so.config to contain the directory where the library
is located, and then run ldconfig (as root)
shared libraries are found by using a combination of LD_LIBRARY_PATH
and the ld.so.config file. if a library cannot be found that way
(though strictly, there are a couple of other (bad) options), then you
get the error you've encountered.
--p
8010
days inactive
8011
days old
linux-audio-dev@lists.linuxaudio.org
3 comments
3 participants
participants (3)
-
Erik de Castro Lopo -
Paul Davis -
Rohan Parkes