On 6/22/17 4:01 PM, Robert Dailey wrote:
> In my toolchain file for Android NDK, I specify the following *.so
> paths manually:
>
> set( ANDROID_PREBUILT_LIBRARIES
>
> ${CMAKE_ANDROID_NDK}/sources/cxx-stl/gnu-libstdc++/4.9/libs/x86/libgnustl_shared.so
> ${CMAKE_ANDROID_NDK}/platforms/android-15/arch-x86/usr/lib/libz.so
> )
>
> However, I'd like a better way to find these files: I already
> configure CMake 3.8 using built-in Android support. It's able to
> configure my toolchain just fine. Can I leverage some built-in
> functionality to get the path to these files? I'm worried with the way
> it is, if I change the other variables that the paths won't be valid
> anymore and I'll have to update them manually again.
I would suggest that you dump all cmake variables and have a look what's
matching your paths:
get_cmake_property(_variableNames VARIABLES)
foreach (_variableName ${_variableNames})
message(STATUS "${_variableName}=${${_variableName}}")
endforeach()
Hope that helps!
Cheers,
Gregor
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
