oss/luanti
oss/luanti
1
0
Fork 0
mirror of https://github.com/luanti-org/luanti.git synced 2025-09-15 18:57:08 +00:00
Code Wiki Activity

DOCS: replace Minetest -> Luanti, minetest. -> core. (#15292)

Browse source 
Co-authored-by: grorp <gregor.parzefall@posteo.de>
This commit is contained in:
Zughy 2024-10-22 23:05:41 +02:00 • committed by GitHub
parent aa273119f2
commit d52e4cdbdb
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
23 changed files with 873 additions and 865 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/developing/os-compatibility.md
View file

@ -2,7 +2,7 @@ OS/library compatibility policy
===============================
This document describes how we decide which minimum versions of operating systems, C++ standards,
libraries, build tools (CMake) or compilers Minetest requires.
libraries, build tools (CMake) or compilers Luanti requires.
Most important is that we do not increase our minimum requirements without a reason or use case.
A reason can be as simple as "cleaning up legacy support code", but it needs to exist.
@ -54,7 +54,7 @@ OpenGL ES 2.0 is supported for the sake of mobile platforms.
It has been [proposed](https://irc.minetest.net/minetest-dev/2022-08-18) moving to OpenGL 2.x or 3.0 with shaders required.
General **system requirements** are not bounded either.
Being able to play Minetest on a recent low-end phone is a reasonable target.
Being able to play Luanti on a recent low-end phone is a reasonable target.
## On totality
@ -71,7 +71,7 @@ Sound is optional at build-time but nobody would call an engine build without so
In general also consider:
* Is the proposition important enough to warrant a new dependency?
* Can we make it easier for users to build the library together with Minetest?
* Can we make it easier for users to build the library together with Luanti?
* Maybe even vendor the library?
* Or could the engine include a transparent fallback implementation?