[New package]bgfx

[Pevernow]

What is it? Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library. Homepage: https://github.com/bkaradzic/bgfx

[Biswa96]

Do you know the proper way to build it with mingw toolchain? bgfx, bx, bimg repositories compile other dependent projects and all the Vulkan related ones which is time consuming and futile as those are already available here.

[lvdpower]

0. install MSYS2 to C:\msys64
1. Set MINGW system variable = "C:/msys64/mingw64/"
2. Set MINGW_HOME system variable = "C:/msys64/mingw64/"
3. start mingw64.exe and you will be at home folder inside MSYS2
4. now get bgfx via git (before this point git client must be installed of course!)

git clone git://github.com/bkaradzic/bx.git git clone git://github.com/bkaradzic/bimg.git git clone git://github.com/bkaradzic/bgfx.git

5. cd bgfx
6. make help
7. make mingw-gcc-release64

Compilation must start here!

Timur

[lvdpower]

Do you know the proper way to build it with mingw toolchain? bgfx, bx, bimg repositories compile other dependent projects and all the Vulkan related ones which is time consuming and futile as those are already available here.

install MSYS2 to C:\msys64
Set MINGW system variable = "C:/msys64/mingw64/"
Set MINGW_HOME system variable = "C:/msys64/mingw64/"
start mingw64.exe and you will be at home folder inside MSYS2
now get bgfx via git (before this point git client must be installed of course!)

git clone git://github.com/bkaradzic/bx.git git clone git://github.com/bkaradzic/bimg.git git clone git://github.com/bkaradzic/bgfx.git

cd bgfx
make help
make mingw-gcc-release64

Compilation must start here!

Timur

[Biswa96]

Many Eternity Later...

I have compiled bgfx with mingw-w64 after some tweaking. Can anyone provide information about how the program should be packaged?

• There is no tags in the repositories. So, the package has to be built from git repository.
• The compiled binaries are linked with bundled 3rd party libraries (e.g. spirv-tools, glslang etc.). Should those be linked with our own mingw packages?
• The compiled binaries are named with build config as suffixes. Should those be named/installed like that?

Inspired by @spectralcascade's tweet https://twitter.com/spectralcascade/status/1568982154146635778

[bkaradzic]

The compiled binaries are linked with bundled 3rd party libraries (e.g. spirv-tools, glslang etc.). Should those be linked with our own mingw packages?

In case of bgfx definitely no. And probably this rule can be applied in general case, because you never know if there are some modifications to vendored libs, or which exact version they are. So it's better to keep it as-is, and avoid headache of you having to track all that.