Re: [CMake] find_file - strange behavior when using Android toolchain

2019-07-31 Thread Eric Doenges
Am 31.07.19 um 08:20 schrieb Stephan Menzel: Hello all, I'm trying to adapt my CMake based toolchain to Android and I'm noticing very strange behavior that I'd like to ask about. My toolchain is C++ based with some dependencies such as Boost, OpenSSL or protobuf. So far it works on a variety o

Re: [CMake] find_file - strange behavior when using Android toolchain

2019-07-31 Thread ugesh reddy
Hi, I also have the same issue with find_file/find_path/find_package when I use the Android NDK and Eric's explanation make sense. One way to solve this find_file(AWSSDK_CORE_HEADER_FILE Aws.h "${AWSSDK_ROOT_DIR}/${AWSSDK_INSTALL_INCLUDEDIR}/aws/core" "${AWSSDK_DEFAULT_ROOT_DIR}/${A

Re: [CMake] find_file - strange behavior when using Android toolchain

2019-07-31 Thread ugesh reddy
Hi, Sorry a small correction. There is no such thing as "NO_CMAKE_SYSROOT". find_file(AWSSDK_CORE_HEADER_FILE Aws.h "${AWSSDK_ROOT_DIR}/${AWSSDK_INSTALL_INCLUDEDIR}/aws/core" "${AWSSDK_DEFAULT_ROOT_DIR}/${AWSSDK_INSTALL_INCLUDEDIR}/aws/core" NO_CMAKE_FIND_ROOT_PATH *

Re: [CMake] find_file - strange behavior when using Android toolchain

2019-07-31 Thread Stephan Menzel
Thank you, Eric and Ugesh, Am Mi., 31. Juli 2019 um 09:16 Uhr schrieb Eric Doenges : > My experience has been that find_file and friends behave in unexpected > ways when you set CMAKE_SYSROOT. In our toolchain files, we set > set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER) > set(CMAKE_FIND_ROOT_PATH

Re: [CMake] find_file - strange behavior when using Android toolchain

2019-07-31 Thread Eric Noulard
Le mer. 31 juil. 2019 à 11:19, Stephan Menzel a écrit : > Thank you, Eric and Ugesh, > > Am Mi., 31. Juli 2019 um 09:16 Uhr schrieb Eric Doenges >: > >> My experience has been that find_file and friends behave in unexpected >> ways when you set CMAKE_SYSROOT. In our toolchain files, we set >> se

[CMake] find_program doesn't use the PATH

2019-07-31 Thread Braden McDaniel
I was tempted to go ahead and file a bug on this; but it seems so basic that I figure I must be missing something. Per the documentation for find_program: If NO_DEFAULT_PATH is not specified, the search process is as follows: ⋮ 5. Search the standard system environment variables.

Re: [CMake] find_program doesn't use the PATH

2019-07-31 Thread Kornel Benko
Am Mittwoch, 31. Juli 2019, 12:19:48 CEST schrieb Braden McDaniel: > I was tempted to go ahead and file a bug on this; but it seems so basic > that I figure I must be missing something. > > Per the documentation for find_program: > >If NO_DEFAULT_PATH is not specified, the search process is

Re: [CMake] find_program doesn't use the PATH

2019-07-31 Thread Braden McDaniel
On Wed, 2019-07-31 at 20:32 +0200, Kornel Benko wrote: > The find_program() is searching something like "/usr/bin/NAME". > "NAME" should be a placeholder. > What you had in mind was probably the second form > find_program(GETTEXT_MSGMERGE_EXECUTABLE NAMES msgmerge) > Mark the string "NAMES".