libtcod-vcpkg-template VS imgui

It doesn't teach on its own, but the libtcod-vcpkg-template can help with quickly setting up Vcpkg and libtcod in a cross-platform manner. Parts might need to be updated to work with C++20 or later. This template also creates Emscripten builds.

Hello all. I'm trying to get the libtcod example project to compile, but seem to be running into errors at every step. When I compile normally and run the binary, I get the error:

I've just checked, and Visual Studio can build/run the libtcod template. So if you setup a CMakeLists.txt to use Vcpkg then your project should run even without VSCode's CMake Tools plugin.

libtcod | GitHub | Issues | Forum | Changelog | Documentation | Template

I'm working in C++17 and doing the ancient C++ tutorial on RogueBasin. I'm starting from the libtcod C++ template and plan on using the latest libtcod features rather than the older ones taught by that tutorial. My new repository is here.

Libtcod's Vcpkg template could work for your conditions. The tools it uses are cross-platform, using VSCode as the IDE rather than Visual Studio, but running CMake manually should work also.

I've made this template project, but I've since modified it so that I can use it to develop libtcod with, so right now it only uses Vcpkg to fetch the dependencies for libtcod and then builds libtcod from a submodule. This template is complete as-is and will compile and run if you follow the instructions.

I've updated the C++ template project to upload build artifacts (listed as automated-builds in any passing workflow.) It also automatically publishes builds as GitHub Releases when you push an annotated tag to the repository. I added one of the libtcod fonts too so that it's clear how to handle data assets in a project.

The GitHub releases don't include a Linux binary, you'll have to compile it yourself. The easiest way is to use the template project which is cross-platform.

libtcod | GitHub | Issues | Forum | Changelog | Documentation | Template

include(cmake/CPM.cmake) function(raylib_imgui_setup_dependencies) message(STATUS "Include Dear ImGui") FetchContent_Declare( ImGui GIT_REPOSITORY https://github.com/ocornut/imgui GIT_TAG 277ae93c41314ba5f4c7444f37c4319cdf07e8cf) # v1.90.4 FetchContent_MakeAvailable(ImGui) FetchContent_GetProperties(ImGui SOURCE_DIR IMGUI_DIR) add_library( imgui STATIC ${imgui_SOURCE_DIR}/imgui.cpp ${imgui_SOURCE_DIR}/imgui_draw.cpp ${imgui_SOURCE_DIR}/imgui_widgets.cpp ${imgui_SOURCE_DIR}/imgui_tables.cpp) target_include_directories(imgui INTERFACE ${imgui_SOURCE_DIR}) include(cmake/CPM.cmake) message(STATUS "Include dbg-macro") cpmaddpackage( "gh:sharkdp/dbg-macro#fb9976f410f8b29105818b20278cd0be0e853fe8" )# v0.5.1 message(STATUS "Include fmtlib") cpmaddpackage("gh:fmtlib/fmt#e69e5f977d458f2650bb346dadf2ad30c5320281" )# 10.x message(STATUS "Include raylib") cpmaddpackage("gh:raysan5/raylib#ae50bfa2cc569c0f8d5bc4315d39db64005b1b0" )# v5.0 message(STATUS "Include spdlog") cpmaddpackage("gh:gabime/spdlog#7c02e204c92545f869e2f04edaab1f19fe8b19fd" )# v1.13.0 message(STATUS "Include rlImGui") FetchContent_Declare( rlImGui GIT_REPOSITORY https://github.com/raylib-extras/rlImGui GIT_TAG d765c1ef3d37cf939f88aaa272a59a2713d654c9) FetchContent_MakeAvailable(rlImGui) FetchContent_GetProperties(rlImGui SOURCE_DIR RLIMGUI_DIR) add_library(rlimgui STATIC ${rlimgui_SOURCE_DIR}/rlImgui.cpp) target_link_libraries(rlimgui PRIVATE imgui raylib) target_include_directories(rlimgui INTERFACE ${rlimgui_SOURCE_DIR}) endfunction()

Immediate mode is a fuzzy concept, as witnessed by this writeup: https://github.com/ocornut/imgui/wiki/About-the-IMGUI-paradi...

It's fun to see the evolution in e.g. these examples of image loading for Dear Imgui:

https://github.com/ocornut/imgui/wiki/Image-Loading-and-Disp...

DirectX9 will even load the image for you, DirectX11 okay we get a few more structures to fill out, DirectX12 is where it goes off the rails and we are filling out a bunch of UNKNOWN DONT_CARE JUST_DO_IT. Then of course Vulkan is the one that gets the big fat "this probably won't actually work for you" warning.

I understand whats happening, but you know sometimes I just want to display a fucking image.

ImGui is engine/GPU agnostic

Themeing isn't a just a retained mode thing, you can do wonders with immediate UIs, even thought (dear)ImGui doesn't provide much, you can still do wonders: https://github.com/ocornut/imgui/issues/707#issuecomment-362...

More on that topic: https://www.youtube.com/watch?v=Z1qyvQsjK5Y

Bonus: If you want to make desktop app with UI, then this is another great C++ library and it's also simple to learn as well. https://github.com/ocornut/imgui.

AFAIK the Rust equivalent to C++'s Dear ImGui is egui.

They use a Dear ImGui, a C++ GUI library.

Aside from bugs and driver issues, Wayland has some unfortunate design limitations. For example, Dear ImGui multi-viewports don't work because "Wayland doesn't let application read or write windows positions."

https://github.com/ocornut/imgui/wiki/Multi-Viewports

This is a feature available on Windows, macOS, and of course X11. Making choices like this means desktop Linux becomes even more of a weird island that nobody wants to support.