libtcod-vcpkg-template VS Doryen

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

Aw, thanks friend! Just using libtcod and a handful of basic ones for maths-related stuff and saving/loading, nothing remotely specialist on that side of things. All the code for generating graphics for instance is based on libtcod, but definitely using the functionality in novel ways!

See the libtcod repo for everything. The contributing file has info on how to configure CMake. Feel free to make an issue, discussion, or PR there if any changes are needed or you have anything you want to ask about.

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

Today I'm back to working on Pataro, the roguelike built on libtcod that made up much of my Hacktoberfest efforts. I had been assigned to an issue requesting the addition of serialization and deserialization, but unfortunately ran out of time and wasn't able to finish the former or start the latter. I ran into issues with Cereal, and had a hard time figuring out the structure of the program and how to go about implementing serialization for all the relevant components. At the end of that attempt I mentioned that if I were to try again I'd start by testing out Cereal separately and getting a handle on that before trying to implement it in Pataro - so that's what I'm doing today.

One of the biggest problems I've faced while tackling this has been figuring out the structure of the program. I've never worked on a game before so the structure of how all the different pieces fit together is alien to me, but I've been slowly figuring it out over the past days and weeks. After getting in touch with the developer of (Pataro)[https://github.com/SuperFola/pataro] and reading tutorials on developing with (libtcod)[https://github.com/libtcod/libtcod] I think I have a better idea of how to approach it.

This month I'm working on participating in Hacktoberfest, starting with contributing to a roguelike game called Pataro built on the libtcod roguelike development library. I chose to work on adding a serialization mechanism to save the player's progress and so far it's involved a lot of new and challenging processes. I haven't completed my work yet but wanted to start sharing progress on my learning and status.

If you're willing to stick to the terminal for now, libtcod is popular for tutorials on building roguelikes.

The same thing happened to me as happened to you, I also hate Libtcod, and it's because of its poor code interpolation with C++ and its null documentation, so I also decided to create a Fork and work on it, the result, an ASCII render with a simple to use, scalable, clean and maintainable interface.

libtcod | GitHub | Issues | Forum | Changelog | Documentation

Like you, I also had the same problem when reviewing the Libtcod code, so I decided to write an engine based on the Libtcod 1.5 code, I am currently still working on it, and I plan to add elements to it to make interfaces using flexbox layout.