libtcod VS MSBuild

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

Libtcod itself uses SDL2. It maps tile glyphs to a texture atlas and maps Unicode codepoints to tile positions. Then it has another data structure called a console which has the background color, foreground color, and codepoint for each tile on that console. It then uses SDL_RenderGeometry to quickly render the background and colored glyphs to an SDL texture, skipping unchanged tiles as an optimization, then renders that texture to the window. The C99 source is here: renderer_sdl2.h renderer_sdl2.c, a C++ version would surely look better.

libtcod has always been a favorite of mine. Does a lot of things to zero fanfare outside the indie roguelike scene.

I've ended up recovering the old 1.3.2 to 1.5.0 builds of libtcod. You can find them on the GitHub releases page. Most of, maybe all of the other places which had these builds are down, but thankfully Jice still had copies of these builds.

FoV is a port from C -> Java of the algorithm found here

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

Hey man, I don't wanna piss in your cherrios if you're intentionally doing it all the hard way, but you know about tcod right? https://github.com/libtcod/libtcod/

Browsing the repo, looks like it has a full C only API, https://github.com/libtcod/libtcod/blob/master/src/libtcod/libtcod.h

libtcod support for terminals is in progress at least for ANSI true colour, and I have a minimal compatibility layer for UNIX only.

I did get confirmation that the actual kill has been postponed to .Net 9.0 rather than .Net 8.0 . However, that PR is factually wrong regarding when System.Runtime.Serialization use became opt-in -- I had to counter-adjust Rogue Survivor Revived to opt into using System.Runtime.Serialization for .Net 7.0, last November i.e. Nov 2022.

Like this https://github.com/dotnet/msbuild/blob/d0060335c1fb2f0523b1cf4656c464c5c4316783/src/Framework/NativeMethods.cs

Here is a taste of what to expect: https://github.com/dotnet/msbuild

The main thing they do is to list projects so that you can open a solution and see a set of projects, or build a solution and build everything there. They also give a lot of customization and fortunately it's rare that you need to know anything about that. It does feel somewhat unnecessary since you should be able to open a project with its dependencies. Hopefully solution files are going to be cleaned up: https://github.com/dotnet/msbuild/issues/1730

Since the previous check, the project has grown a lot. Our analyzer has become more advanced, too. This only makes this task more interesting! Despite the high quality of the MSBuild product and the well-known name of its creator, we again managed to find some issues in MSBuild's source code. The project is almost entirely written in C#. You can see it on GitHub. We took the code from this commit.

relevant github issue: https://github.com/dotnet/msbuild/issues/1730

msbuild is the "make" system, but for .Net. Those .csproj files are just makefiles by another name. Also, msbuild is not Windows-only. The readme specifically states that it can run on Unix (and Unix-like) systems that support .Net Core.

You can't do without source files when you want to better understand what is happening "under the hood" of a particular system. For example, do you want to improve your understanding of how types from the standard library work? The source code of .NET Framework and .NET will help you to do that. Do you want to dig deeper into the compiler? No problem - here is the Roslyn's source code at your service. Do you need to look inside the build system? Here you go - the MSBuild code is also open-source. By the way, if you are interested in build processes, you may also find MSBuild Structured Log Viewer useful. It's a tool that allows you to work with MSBuild build logs in a convenient format.