Displaying 5 results from an estimated 5 matches for "link_librari".
Did you mean:
link_libraries
2013 Sep 03
4
[LLVMdev] Adding a library to CMake deps
Hi folks,
When cross-compiling LLVM to ARM, using CMake+Ninja, I realized that
libxml2 depends on lzma, but the dependency is not explicit on the
build.ninja file under the "build bin/c-index-test"'s LINK_LIBRARIES (which
is the only one that cares about it).
I couldn't find the place to add -llzma into the deps, and the only mention
of libxml2 is in config-ix.cmake:
find_package(LibXml2)
if (LIBXML2_FOUND)
set(CLANG_HAVE_LIBXML 1)
endif ()
Which I could do the same with lzma? Any ideas on what the...
2013 Sep 03
0
[LLVMdev] Adding a library to CMake deps
On 09/03/2013 02:13 PM, Renato Golin wrote:
> Hi folks,
>
> When cross-compiling LLVM to ARM, using CMake+Ninja, I realized that
> libxml2 depends on lzma, but the dependency is not explicit on the
> build.ninja file under the "build bin/c-index-test"'s LINK_LIBRARIES
> (which is the only one that cares about it).
>
> I couldn't find the place to add -llzma into the deps, and the only
> mention of libxml2 is in config-ix.cmake:
>
> find_package(LibXml2)
> if (LIBXML2_FOUND)
> set(CLANG_HAVE_LIBXML 1)
> endif ()
>
> Which...
2013 Sep 03
0
[LLVMdev] Adding a library to CMake deps
Renato Golin <renato.golin at linaro.org> writes:
> When cross-compiling LLVM to ARM, using CMake+Ninja, I realized that
> libxml2 depends on lzma, but the dependency is not explicit on the
> build.ninja file under the "build bin/c-index-test"'s LINK_LIBRARIES (which
> is the only one that cares about it).
>
> I couldn't find the place to add -llzma into the deps, and the only mention
> of libxml2 is in config-ix.cmake:
>
> find_package(LibXml2)
> if (LIBXML2_FOUND)
> set(CLANG_HAVE_LIBXML 1)
> endif ()
>
> Which...
2017 Nov 16
2
Correctly linking against libLLVM (single shared library build)
...sage(STATUS "Using LLVMConfig.cmake in: ${LLVM_DIR}")
llvm_map_components_to_libnames(llvm_libs support core irreader)
message(STATUS "Components mapped to libnames: ${llvm_libs}")
add_executable(bubak a.c)
llvm_config(bubak support core irreader)
get_target_property(LL bubak LINK_LIBRARIES)
message(STATUS "Components mapped by llvm_config: ${LL}")
It results in:
-- Found LLVM 4.0.1
-- Using LLVMConfig.cmake in: /usr/lib64/cmake/llvm
-- Components mapped to libnames: LLVMSupport;LLVMCore;LLVMIRReader
-- Components mapped by llvm_config: LLVMSupport;LLVMCore;LLVMIRReader...
2017 Oct 23
2
Correctly linking against libLLVM (single shared library build)
Hi,
In SUSE we have recently switched from building LLVM as multiple shared
libraries (using BUILD_SHARED_LIBS) to building it as a single shared library
(using LLVM_BUILD_LLVM_DYLIB).
The multiple shared libraries build was causing issues and apparently it is
only meant for LLVM developers. Our guidelines prohibit linking against static
libraries unless there is no other option.
After this