-
Notifications
You must be signed in to change notification settings - Fork 7
modify code to allow shared object used independently and some minor changes #7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
hwyao
wants to merge
2
commits into
nosnoc:main
Choose a base branch
from
hwyao:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment 1:
The
IMPORTED_NO_SONAME TRUE
for qpOASES is that,libqpOASES.so
has no SONAME. This might be a reason that here we directly uses theMakefile
instead ofCMakeLists.txt
provided by the repo.(SONAME can be check with
readelf -d <library-name> | head -10
to comparelibosqp.so
andlibqpOASES.so
)When not using the
IMPORTED_NO_SONAME
, the runtime dynamic linking of the library is based on the relative path, instead of therpath
. Simply speaking, when you try to run the library / executable in a folder that is not the folder that you runmake
command, the loading will be failed.We can inspect this by running the
ldd
over the builtliblcqpow.so
:(no fixing) inside build folder:
>~/Git/LCQPow/build$ ldd ./lib/liblcqpow.so linux-vdso.so.1 (0x00007ffc4808e000) lib/libqpOASES.so (0x00007f62c680d000) ...
(no fixing) in some other folder:
(fixed) everywhere:
Some helpful references:
https://cmake.org/cmake/help/latest/prop_tgt/IMPORTED_NO_SONAME.html
https://stackoverflow.com/questions/10199045/c-linker-missing-library-when-running-soname-behavior
https://stackoverflow.com/questions/68164903/cmake-to-link-external-library-with-import-soname-ro-import-location