GLFW VS Open-Source Vulkan C++ API

There is a pattern to it which is usable with every GitHub repository. For example, GLFW v3.3.8 can be fetched from: https://github.com/glfw/glfw/archive/refs/tags/3.3.8.tar.gz

What exactly would I fetch with this method? He's fetching a raylib url, but I don't really see a pattern in it I can follow when fetching glfw. I assume I can use this repository? https://github.com/glfw/glfw

I'm not sure how to fix it, sorry. I searched for some of the messages and found this bug: . I think overriding the LWJGL library might fix the issue, but I don't see any way to do that with the CurseForge launcher.

To go multiplatform with OpenGL / Vulkan (harder for a beginner) you can use a simple window library like GLFW and Dear ImGui for UI. I use these for Avoyd, along with a few other libraries.

cmake_minimum_required(VERSION 3.16) project(P1_PR) add_executable(P1_PR src/main.cpp ) find_package(GLFW QUIET) if(NOT GLFW_FOUND) message(STATUS "GLFW not found, fetching from GitHub...") include(FetchContent) FETCHCONTENT_DECLARE( GLFW GIT_REPOSITORY https://github.com/glfw/glfw/ GIT_TAG 3.3.8 ) FetchContent_GetProperties(GLFW) if (NOT GLFW_POPULATED) set(FETCHCONTENT_QUIET NO) FetchContent_Populate(GLFW) set(BUILD_EXAMPLES OFF CACHE BOOL "" FORCE) set(BUILD_GAMES OFF CACHE BOOL "" FORCE) add_subdirectory(${glfw_SOURCE_DIR} ${glfw_BINARY_DIR}) endif() endif() find_package(GLEW QUIET) if(NOT GLEW_FOUND) message(STATUS "GLEW not found, fetching from GitHub...") include(FetchContent) FETCHCONTENT_DECLARE( GLEW GIT_REPOSITORY https://github.com/Perlmint/glew-cmake GIT_TAG glew-cmake-2.2.0 ) FetchContent_GetProperties(GLEW) if (NOT GLEW_POPULATED) set(FETCHCONTENT_QUIET NO) FetchContent_Populate(GLEW) set(BUILD_EXAMPLES OFF CACHE BOOL "" FORCE) set(BUILD_GAMES OFF CACHE BOOL "" FORCE) add_subdirectory(${glew_SOURCE_DIR} ${glew_BINARY_DIR}) endif() endif() target_include_directories(${PROJECT_NAME} PRIVATE ${GLFW_SOURCE_DIR} PRIVATE ${GLEW_SOURCE_DIR} ) target_link_libraries(${PROJECT_NAME} glfw glew32 opengl32 gdi32 glm ) target_compile_features(${PROJECT_NAME} PRIVATE cxx_std_20)

I recently started following the Learn OpenGL tutorial and noticed that when I create a window with GLFW in the Wayland GNOME session the cursor becomes much larger when hovering over the window. This is because a Wayland client is expected to define its own pointer (cursor) and that seems to lead to inconsistencies between implementations. I do not have a problem with CSD being default on Wayland (I even prefer it when done really well, like Telegram Desktop, or any GTK app with GtkHeaderBar) but the cursor switching scale while moving it over surfaces (windows) is much more jarring.

I recall an issue specific to Wayland where windows only appear after the first command buffer is submitted. https://github.com/glfw/glfw/issues/1398

Or the vulkan.hpp RAII samples would be a good place?

For a real-life example: consider the vk::raii namespace of Vulkan-Hpp, where the developers have posted examples. The vk::raii::su namespace has a bunch of free functions that one might think are associated with a Vulkan instance/object (in fact, the Vulkan Tutorial does implement them as member functions), but they are much nicer when used as pure functions. It keeps the class/struct definition itself nice and clean.

VS 2022 has seen a massive increase in performance especially after its move to 64-bit. It lints even the largest headers (ahem, Vulkan-Hpp) in a matter of seconds whereas CLion just chokes and crashes.

So I am attempting to follow the Vulkan Tutorial, but I am trying to use decidedly more C++ than the tutorial suggests, by using the Vulkan-Hpp C++ bindings and the vk::raii classes, in particular.

Its literally a few kb: https://github.com/KhronosGroup/Vulkan-Hpp/tree/master/vulkan Why on earth are you downloading all the samples and what not? Just use the hpp files and be done with it. SMH

All the current major game engines are C++. C hasn't been widely used since the Quake 3 days.

While yes the Vulkan & OpenGL APIs are pure C, that's very, very little of what you actually code against. You very quickly abstract that or use a middleware like bgfx or whatever. In the case of Vulkan while the spec API is C, there's first-class C++ wrappers/bindings provided as well: https://github.com/KhronosGroup/Vulkan-Hpp

And other than Vulkan & OpenGL, you'll find that most other APIs/libraries in the space are C++, not C. Valve's libraries are C++. Dear ImGui is C++. Bullet & PhysX are C++. Microsoft's glTF SDK is C++. etc...

You can argue endlessly about how "true C++" those all are or if they're just "C with namespaces" but that's largely irrelevant - they aren't C and they need a C++ compiler.

Having this on the side and reading the actual implementation is in my opinion the best way to learn about using Vulkan compute and how the different parts of Vulkan are related. On the other hand you need to be at least little bit familiar with concepts of Vulkan (and vulkan.hpp) to understand it and know how would things change if you would change some options.

vulkan_structs.hpp - part of the Vulkan-Hpp library (Vulkan bindings for C++) comes in at 97967 lines of code.

https://github.com/KhronosGroup/Vulkan-Hpp/issues/926#issuecomment-810979142