This is precisely the scenario that the CMAKE_TRY_COMPILE_PLATFORM_VARIABLES <https://cmake.org/cmake/help/latest/variable/CMAKE_TRY_COMPILE_PLATFORM_VARIABLES.html> variable is meant for. It allows a toolchain file to specify additional variables that should be passed along to try_compile().
On Fri, Feb 1, 2019 at 6:36 AM Shoaib Meenai <smee...@fb.com> wrote: > We have a somewhat similar problem with LLVM's toolchain file for > cross-compiling to Windows, and we solve it there by saving and restoring > cache variables from the environment inside the toolchain file itself. See > https://reviews.llvm.org/diffusion/L/browse/llvm/trunk/cmake/platforms/WinMsvc.cmake;352783$88-102?as=source&blame=off > and the subsequent calls to init_user_prop. > > On 1/31/19, 12:19 AM, "CMake on behalf of tors...@robitzki.de" < > cmake-boun...@cmake.org on behalf of tors...@robitzki.de> wrote: > > Hi Sergei, > > > Am 31.01.2019 um 08:42 schrieb Sergei Nikulov < > sergey.niku...@gmail.com>: > > > > Just guessing maybe better use $ENV{ARM_GCC_TOOL_PATH} ? > > https://cmake.org/cmake/help/latest/variable/ENV.html?highlight=env > > Well, but this would mean, I had to configure CMake not only with > Cache variables: > > cmake > -DARM_GCC_TOOL_PATH=/usr/local/gcc-arm-none-eabi-7-2018-q2-update > -DBINDING=nrf52 -DCMAKE_TOOLCHAIN_FILE=../cmake/gcc-arm-none-eabi.cmake > -DNRF5_SDK_ROOT=~/CMSIS/nRF5_SDK_14-2/ .. > > But also with environment variables: > ARM_GCC_TOOL_PATH=/usr/local/gcc-arm-none-eabi-7-2018-q2-update cmake > -DBINDING=nrf52 -DCMAKE_TOOLCHAIN_FILE=../cmake/gcc-arm-none-eabi.cmake > -DNRF5_SDK_ROOT=~/CMSIS/nRF5_SDK_14-2/ .. > > Thanks for the pointer, I will think about it. > > kind regards, > Torsten > -- Craig Scott Melbourne, Australia https://crascit.com Get the hand-book for every CMake user: Professional CMake: A Practical Guide <https://crascit.com/professional-cmake/>
-- 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: https://cmake.org/mailman/listinfo/cmake
