Re: [CMake] file(TO_NATIVE_PATH ... ) and cross-compiling

Unfortunately I encountered exactly the same problem. It would be nice to describe in documentation that file(TO_NATIVE_PATH ...) means "native for target system" and also would be nice to introduce the file(TO_HOST_NATIVE_PATH ...) subcommand. On 26.3.2018 19:40, Miroslav Keš wrote: > I'm cros

Re: [CMake] file(TO_NATIVE_PATH ... ) and cross-compiling

I'm cross-compiling in Windows to another target system (VxWorks) but this is not so important. I thought the idea behind the TO_NATIVE_PATH option was that the internal CMake path representation could be transformed to the system native path so that external programs that rely on the native pa

Re: [CMake] file(TO_NATIVE_PATH ... ) and cross-compiling

Disclaimer: I cannot speak to intent, and have never used these before. So since you’re cross compiling, when looking at the docs ( https://cmake.org/cmake/help/v3.0/command/file.html ), I think you can get away with using TO_CMAKE_PATH. I

[CMake] file(TO_NATIVE_PATH ... ) and cross-compiling

Hi! I have question concerning the file(TO_NATIVE_PATH ...) behavior. The documentation says: "The TO_NATIVE_PATH mode converts a cmake-style into a native path with platform-specific slashes (\ on Windows and / elsewhere)."  ... but it doesn't say if the decision is made based on the CMAKE_SYS

[CMake] file(TO_NATIVE_PATH ... ) and cross-compiling

Hi! I have question concerning the file(TO_NATIVE_PATH ...) behavior. The documentation says: "The TO_NATIVE_PATH mode converts a cmake-style into a native path with platform-specific slashes (\ on Windows and / elsewhere)." ... but it doesn't say if the decision is made based on the CMAKE_SY