Chris Thrasher

> Might also be mitigated by using the -S flag. The README is already explicit about `-S .` in the build instruction. > feel like this is the kind of...

Good point about not over-filling the README which I maybe have already done. I'll think on this more as I hopefully get more feedback from people using this template. I'll...

I think the usage instructions are pretty good as-is so I'm closing the issue.

I've used that workaround before, in particular to avoid installing a testing framework. It works well in my experience. In this case I think our best option is to simply...

What do you think about simply removing that `install` command? Installing programs with runtime assets is not trivial and is out of the scope of this template so I'd rather...

> I don't want to scrap together the necessary files from the build directory, whenever I want to put together a clean build. I'm not sure what this means.

Discussions in Discord are showing that writing a correct install system that installs everything required _and nothing more_ is not easy. If we're willing to install lots of unnecessary SFML...

I still think this is the right thing to do. We simply can't figure out a good one-size-fits-all solution for installation so it's not good to provide a half-baked solution...

If linking multiple libraries is required then that hints at the fact that the SQLiteCpp target is missing some `PUBLIC` dependencies. That's the modern CMake solution and is preferable to...

DLL issues are causing CI to fail. We need to make sure all of the SFML and CSFML DLLs exist in the same directory as the test executables but for...