←back to thread

101 points NormalExisting | 1 comments | | HN request time: 0.788s | source

Been making this rasterizer engine in C++ for the past few months, now also adding ray-tracing functionality to the system.

Simply load a model or generate a mesh, add some lights, and render.

Show context
DrFalkyn ◴[] No.43343281[source]
If portability is a goal you might want to use CMake and Docker.
replies(2): >>43343309 #>>43344650 #
johnnyjeans ◴[] No.43343309[source]
make is more portable than cmake. docker has zero value add from what I saw in the repo.
replies(3): >>43343564 #>>43343587 #>>43344017 #
psyclobe ◴[] No.43344017[source]
Make is quite a bit more headache these days to consume then make (in modern code bases anyway).
replies(1): >>43345532 #
1. johnnyjeans ◴[] No.43345532[source]
I'm not actually a fan of make, I think mk is a much better language, but everything is relative. I still prefer make over any meta-build system or garbage like boost jam. In my experience the problem of modern codebases is that they're structured like crap in the first place. Too complicated and for very little real reason. OP's codebase is actually trivial, so the problem doesn't really exist. It would be trivial to adapt it to use msvc, but if you have make on windows, chances are you already have gcc so there's not much point unless you REALLY want to use microsoft's compiler.