Chadwick Boulay

I have some meetings this morning but I’ll take a look after.

If you ever want to know what top-level options are available to CMake then you can use the cmake-gui. The workflow for the cmake-gui is to Configure, which scans the...

@mgrivich I'd like to know more about your pain points with building LabRecorder so we can write better documentation. Were you using the new repository or the old one? Were...

> The appropriate versions of Qt and boost had to be found and installed. The versions don't matter except Qt > 5.5 on Ubuntu (otherwise 5.x should work) and boost...

FYI I updated [BUILD.md](https://github.com/labstreaminglayer/labstreaminglayer/blob/master/doc/BUILD.md) with a few more details for using Visual Studio 2017. Changing any CMake settings requires editing a CMakeSettings.json file (easily accessible from VS 2017's CMake menu)....

> shows that `QT_DEPLOYQT_EXECUTABLE` is `C:/Qt/5.11.1/winrt_x86_msvc2017/bin/windeployqt.exe` Is there any chance that you have a cached cmake config from a previous attempt that is conflicting? I don't know how this could...

> What do you think of automatically deleting CMakeCache.txt every time that cmake configure is run? It's been a while since I tried using that as a workflow but I...

@mgrivich If you can, please try using VS2017 with its cmake integration to see if you like it and if it propagates variable changes properly. From what I've used so...

> Dependent libraries (such as Qt and lsl) are never copied into Visual Studio target folders, so launch of XDF_Browser (for example) from inside visual studio fails with dlls and...

Sorry I forgot an important detail that I don't want you to miss: When using VS2017's integrated cmake, you don't provide command-line arguments so you have to set boost and...