Hello.
I have a strange issue when cross compiling with CMake.
When i compile for host, in the resulting binary i have:
readelf -d ./test
...
0x0001 (NEEDED) Shared library: [libfoo.so]
0x000f (RPATH) Library rpath: [$ORIGIN/../../lib/]
...
When i use CMake
Does /home/mgh/proj/test/lib/libfoo.so not have a SONAME while your
native libfoo.so does?
The linker may use the SONAME when available and might fall back to the
path as seen on the command line (/home/mgh/proj/test/lib/libfoo.so)
otherwise?
Nils
On 07/19/2013 10:41 AM, Дмитрий Дороговцев
2013/7/19 Nils Gladitz nilsglad...@gmail.com
Does /home/mgh/proj/test/lib/libfoo.so not have a SONAME while your
native libfoo.so does?
The linker may use the SONAME when available and might fall back to the
path as seen on the command line (/home/mgh/proj/test/lib/libfoo.so)
otherwise?
When the library is being created by CMake itself I would have expected
a SONAME by default:
Default is to set soname on all shared libraries and modules as long
as the platform supports it.
Is armLinux a valid value for CMAKE_SYSTEM_NAME?
Quick glimpse at some documentation suggests you may
2013/7/19 Nils Gladitz nilsglad...@gmail.com
When the library is being created by CMake itself I would have expected
a SONAME by default:
Default is to set soname on all shared libraries and modules as long as
the platform supports it.
Is armLinux a valid value for CMAKE_SYSTEM_NAME?
