update copy for code samples that require a bsp #11
Conversation
| provide cmake with the full path to your sample directory. | ||
| >**Note**: If you encounter any issues with long paths when compiling under Windows*, you may have to create your 'build' directory in a shorter path, for example `C:\samples\build`. You can then run cmake from that directory, and provide cmake with the full path to your sample directory, for example | ||
| > ``` | ||
| > C:\samples\build> cmake -G "NMake Makefiles" C:\long\path\to\code\sample\CMakeLists.txt |
There was a problem hiding this comment.
I find this part overkill, don't you think?
There was a problem hiding this comment.
i always find an example helpful.
If I found it overkill i wouldn't have written it :)
There was a problem hiding this comment.
Yeah but here we are showing how to use cmake which is orthogonal to what the sample is trying to show.
We could also explain how to install cmake, etc.
I feel like we should expect people to know how to use the tools (e.g. we expect people to know how to open a terminal, navigate to the appropriate folder, etc.)
We give then the necessary info to run cmake in our particular context (the flags we use), but I don't view it as necessary to give them more general information such as how to run cmake from a different folder than the build directory that we just explained them above
Existing Sample Changes
Description
Readme change
Fixes Issue#
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration