You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I mentioned, I'm in the process of creating python wrappers for ShivaVG. While building these, I discovered a strange problem that only affects 64 bit Linux (I also tested this on 64 bit OS X and 32 bit Linux)
/usr/bin/ld: ../ShivaVG/src/libOpenVG.a(shPath.c.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC
../ShivaVG/src/libOpenVG.a: could not read symbols: Bad value
I got around this by adding the following to the bottom of CMakeLists.txt in the src directory: SET_TARGET_PROPERTIES( OpenVG PROPERTIES COMPILE_FLAGS -fPIC)
I haven't done much linking before, so I'm not very familiar with the process of making and using static and shared libraries. Is the -fPIC flag a silly thing to add in this case? Should I be linking against a shared library instead (which the current system doesn't generate)? Should it be part of the CMake system, and if so, where should it be?
The text was updated successfully, but these errors were encountered:
Not sure whether this is a bug or not.
As I mentioned, I'm in the process of creating python wrappers for ShivaVG. While building these, I discovered a strange problem that only affects 64 bit Linux (I also tested this on 64 bit OS X and 32 bit Linux)
I got around this by adding the following to the bottom of
CMakeLists.txt
in thesrc
directory:SET_TARGET_PROPERTIES( OpenVG PROPERTIES COMPILE_FLAGS -fPIC)
based on http://www.cmake.org/pipermail/cmake/2006-September/011316.html
I haven't done much linking before, so I'm not very familiar with the process of making and using static and shared libraries. Is the
-fPIC
flag a silly thing to add in this case? Should I be linking against a shared library instead (which the current system doesn't generate)? Should it be part of the CMake system, and if so, where should it be?The text was updated successfully, but these errors were encountered: