either. How does cmake determine that a file is an object it can use on
the link line? This is a third party .so, so I'm not quite sure what
they did to build it, but it's likely they did something strange.
Kenny
Bill Hoffman wrote:
Kenneth Chang wrote:
I manufactured a simple setup
about this:
target_link_libraries(a.out /path/to/abcd.so)
If you use find_library(), then you should be getting full names
already.
Clint
Kenneth Chang wrote:
Hi,
I have this third party library that has a .so named like abcd.so
instead of libabcd.so. Putting the name in
target_link_libraries
kch...@fiji:~$ cmake --version
cmake version 2.6-patch 2
Michael Wild wrote:
What version of CMake are you using? Anything before 2.6 used to do
this, newer versions shouldn't.
Michael
On 14. Aug, 2009, at 18:23, Kenneth Chang wrote:
Tried this, ABCD_LIBRARY gets the correct path
EXTERNAL_OBJECT true # if it should be compiled or only linked
GENERATED false # if the obj-files exist before build time
)
- Dominik
Kenneth Chang wrote:
kch...@fiji:~$ cmake --version
cmake version 2.6-patch 2
Michael Wild wrote:
What version of CMake are you using
I did, then cmake broke the .so down into its component paths and
library name, and used -Lpath -llibname, which caused the linker to
look for path/liblibname.so
-Kenny
Bill Hoffman wrote:
Kenneth Chang wrote:
Just downloaded 2.6.4, same behavior.
Do I have to mark the .so extension so
]: *** [CMakeFiles/main.dir/all] Error 2
make[1]: Leaving directory `/local/home/kchang/sandbox/thost'
make: *** [all] Error 2
Bill Hoffman wrote:
Kenneth Chang wrote:
I did, then cmake broke the .so down into its component paths and
library name, and used -Lpath -llibname, which caused the linker
to look
