How do I find the library .so files?

Question

0.00/5 (No votes)

See more:

OK, this has been asked many times, so please bear with me.

My "tool" seems to ignore WHERE it should put library .so files.
I need an EASY way - Linux command - to find them.

clang++ -c -pipe -g -std=gnu++11 -Wall -Wextra -D_REENTRANT -fPIC -DBT_SCAN_LIB_LIBRARY -DQT_QML_DEBUG -DQT_CORE_LIB -I../BT_SCAN_LIB -I. -I/home/nov25-1/Qt/5.15.2/gcc_64/include -I/home/nov25-1/Qt/5.15.2/gcc_64/include/QtCore -I. -I/home/nov25-1/Qt/5.15.2/gcc_64/mkspecs/linux-clang -o bt_scan_lib.o ../BT_SCAN_LIB/bt_scan_lib.cpp
rm -f libBT_SCAN_LIB.so.1.0.0 libBT_SCAN_LIB.so libBT_SCAN_LIB.so.1 libBT_SCAN_LIB.so.1.0
clang++ -ccc-gcc-name g++ -Wl,-rpath,/home/nov25-1/Qt/5.15.2/gcc_64/lib -shared -Wl,-soname,libBT_SCAN_LIB.so.1 -o libBT_SCAN_LIB.so.1.0.0 bt_scan_lib.o  /home/nov25-1/Qt/5.15.2/gcc_64/lib/libQt5Core.so -lpthread    
ln -s libBT_SCAN_LIB.so.1.0.0 libBT_SCAN_LIB.so
ln -s libBT_SCAN_LIB.so.1.0.0 libBT_SCAN_LIB.so.1
ln -s libBT_SCAN_LIB.so.1.0.0 libBT_SCAN_LIB.so.1.0
objcopy --only-keep-debug libBT_SCAN_LIB.so.1.0.0 libBT_SCAN_LIB.so.1.0.0.debug && objcopy --strip-debug libBT_SCAN_LIB.so.1.0.0 && objcopy --add-gnu-debuglink=libBT_SCAN_LIB.so.1.0.0.debug libBT_SCAN_LIB.so.1.0.0 && chmod -x libBT_SCAN_LIB.so.1.0.0.debug

What I have tried:

Tried "whereis" and "find", but I do not know HOW to make these
commands to search in specific path , and actually prefer NOT to have to specify "suspected" path because I cannot even find it there using manual search.

Posted 1-Mar-24 5:46am

Salvatore Terress

Updated 1-Mar-24 8:46am

PIEBALDconsult

v2

Add a Solution

Comments

Richard MacCutchan 1-Mar-24 12:31pm

What tool are you referring to?
What library are you referring to?
How did (think) you installed the libray? Or how did you build it?

Please provide more details.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CPallini · Answer 1 · 2024-03-01T08:39:00

Solution 1

What is 'your tool'?
I you mean the posted command lines, they are creating the shared library files in (their) current directory, I believe.

Posted 1-Mar-24 8:39am

CPallini

k5054 · Answer 2 · 2024-03-01T13:38:00

You could always try locate

Shell

$ sudo apt install -y locate
# ... installation messages snipped ...
$ sudo updatedb
$ locate libc.so
/usr/lib/arm-linux-gnueabihf/libc.so
/usr/lib/arm-linux-gnueabihf/libc.so.6
$

You'll need to run updatedb to initially populate the locate database if you want to run it right away. Otherwise the installed package will set up a cron job to run updatedb overnight.
Be aware that locate only shows you files that you can see. This means that files that are in directories that you do not have search access to will not be shown. But you can always sudo locate somefile to run it as root, which should be able to locate any file on the system.