JoshuaBrookover

If you include this project in a larger one (so that you build bgfx from source each time) and you want to keep the examples around for reference (so they're...

We could have ```BGFX_INSTALL_EXAMPLES``` on by default? It makes sense to minimize confusion for a new user while still providing the flexibility. I suspect any serious project will disable examples...

Yeah, that's what turning ```BGFX_INSTALL_EXAMPLES``` on by default would do. It's a conflated flag because the concept is conflated within CMake itself. By including the examples in the "all" build...

@Qix- Your last question [is the cause for the global include of examples](https://github.com/JoshuaBrookover/bgfx.cmake/commit/9972c1001b44179fb5655ec1bc52fa74a87e7d56). My guess is you (and most others) don't need texturev, so it is an unfortunate arrangement right...

@bkaradzic I think the issue with texturev is a misunderstanding of how CMake works. A bit of explanation, just in case you're curious... This project tries to mimic the bgfx...

> Why not just invert the target_include_directories call to have the examples use the directories instead of putting them as PUBLIC on the production dependencies? Examples and tests should come...

> This isn't an issue on my end. You are suggesting fixes we disagree with, to problems we cannot reproduce. If you want to fix something, you first need to...

Here's the problems as I see it: * if you build tools, you are forced to build all tools * bgfx.cmake force includes example dependencies always * texturev requires examples...

> I think you misunderstood my issues > how you've described the problems as a whole is exactly how I see it If I have described the problem exactly, where...

> Because it's philosophically incorrect. A production tool relying on code from demos or examples is not correct. I agree with you, that is why I listed it as an...