Quote:
Originally Posted by knudfl
When a lib is asked for by configuring or
compiling : l<name> = lib<name>.so , which
is always provided by the '-devel' version of
the library in question.
.....
|
.so files are required for the package to run, hence they usually don't go into -devel packages. -devel stuff packages usually contain header and source files that are needed when compiling,
but are not needed to run the final binary.
Note that the error issued above is not from the compiler either, but from the linker (ld). Since the binaries are linked after being compiled, I think that the -devel stuff must be in place. Otherwise he wouldn't be reaching the linking stage at all.
scarypajamas, if the library (.so) file has been installed manually or using a non-standard package into a non-standard location you might need to pass the path to the library to kdevelop. Don't ask me how, it should be configured in some place on the project properties or wherever.
With gcc in command line you would use -L for that.
You might need also to add the path to your LD_LIBRARY_PATH variable if it isn't already there to be able to run the binary file, unless you link it statically.