User test Feedback

[jacquelinekay]

• Consider setting a standard CMake variable such as KVASIR_TOOLCHAIN_DIR and logic for setting the default instead of having the user set the toolchain variable in their CMakeLists.txt.
• When following the instructions on the README, I get a warning that CMAKE_TOOLCHAIN_FILE is not used. This should probably be removed from the documentation.

[cjsmeele]

• Consider setting a standard CMake variable such as KVASIR_TOOLCHAIN_DIR and logic for setting the default instead of having the user set the toolchain variable in their CMakeLists.txt.

I suppose since we now use CMake toolchain files, we can set the Kvasir toolchain directory automatically from that file instead. I'll see if that works.

• When following the instructions on the README, I get a warning that CMAKE_TOOLCHAIN_FILE is not used. This should probably be removed from the documentation.

This may be caused by re-running cmake with the TOOLCHAIN parameter in an existing (and generated) build directory. Could this be the case?
The toolchain file only needs to be specified when the build directory is first generated.

[jacquelinekay]

Do you guys want to set -std=c++11 or c++14 or whatever standard we've decided on by default?

[CvRXX]

I don't know, I would like toolchain to be usable for other things than to use it for kvasir. And maybe other projects can't run on 11/14