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 
 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 
    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 
    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 
    Thanks for the pointer, I will think about it.
    kind regards,


Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 

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 

Follow this link to subscribe/unsubscribe:

Reply via email to