The big milestone at work is almost over, so I guess I can go back to the Avatar project.
I’ve spend little time on it lately, and only to setup parts of Vulkan initialization (physical device, instance…). I choose to use Vulkan since it’s the more low-level graphic library that the Meta Quest 3 supports, so I hope to have enough room to make something cool with it.
I’ve also decided to convert the projet from C++ back to classic, ansi, C. Why ? Because I’m more confortable with C. I can more easily anticipate problems and think about “what the hardware will do”. For the moment, I’m alone on this project, so it’s no biggy, but if I decide to distribute the engine or add more contributors, maybe we will switch back to C++ (since I know that using C in 2024 is being “old school”, but hey, it’s my project and I’m the only one working with it). I’m not the only one who decided to use C for this kind of project recently, you can check at Raylib.
I will also take the occasion to migrate parts of the documentation to ReStructuredText format and properly setup the CMake file to act as “the main utility” of the project. I think I’ll take example of the Linux kernel for that, where the documentation for the the devs, users, admins and maintainers lived inside the Kernel repository.
Ideally, I would have use only Make, GCC, GDB and ManPages, but since I’m on Windows for my personal laptop… Guess that I’ll do without them. I’ll use PDF downloads for Man, CMake, CL.exe and I still have to masterize WinDbg. I should be able to find my way with that.
I should really find an easiest way to update those ramblings, just to really write as I think.