Бранимир Караџић

@Qix- Because some common functionality between examples, and graphics tools are shared...

It doesn't break anything, it's just inside library named `libexample-common.a`. This might be different with CMake, I'm talking how it's inside bgfx repo. I don't use CMake.

The only libraries you need to use bgfx are: ``` libbgfxDebug/Release.a libbimgDebug/Release.a libbxDebug/Release.a ``` Everything else is for tools or examples.

> I'd be happy to submit a patch to BGFX Don't submit PR. :) This whole thing is nonsense, you're mapping some world view you have to other projects. Build...

The reason why this is preferred: `#include ` is because there tons of stuff inside `meshoptmizer/src` directory that has to be added to include path so you can write `#include...

> There's only one meshoptimizer.h in that directory so I don't really understand your argument. It's general rule, there are other projects that don't cleanly split includes and sources.

> Designing deployment and CI/CD pipelines as well as working on multiple build systems as a career isn't what I'd consider just "some world view". bgfx as library was used...

Do you need geometryc?! If you need it use provided version of meshoptimizer. If you don't need it exclude it from build. I don't know how CMake works. With GENie...

But there is another issue, this implies in CMake include paths are somehow global, not per project.

@wasikuss I extracted your range slider into separate .inl/.h files and using ImGui's user includes for building it together with ImGui. This way it's easier to get integrated to other...