| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, this lua code led to a crash:
local pcg = PcgRandom(42)
local value = pcg:next()
This was because if you called s32 PcgRandom::range(min, max) with the
minimum and maximum possible values for s32 integers (which the lua
binding code did), u32 PcgRandom::range(bound) got called with 0 as the
bound. The bound however is one above the maximum value, so 0 is a "special"
value to pass to this function. This commit fixes the lua crash by
assigning the RNG's full range to the bound 0, which is also fits to the
"maximum is bound - 1" principle, as (u32)-1 is the maximum value in the
u32 range.
|
| |
|
| |
|
| |
|
|
|
|
| |
Also misc. minor cleanups
|
| |
|
|
|
|
| |
Currently translated at 100.0% (270 of 270 strings)
|
| |
|
| |
|
|
|
|
| |
Currently translated at 91.1% (246 of 270 strings)
|
|
|
|
| |
Currently translated at 100.0% (270 of 270 strings)
|
|
|
|
| |
Currently translated at 100.0% (270 of 270 strings)
|
|
|
|
| |
Currently translated at 100.0% (270 of 270 strings)
|
|
|
|
| |
Currently translated at 100.0% (270 of 270 strings)
|
|
|
|
| |
Currently translated at 100.0% (270 of 270 strings)
|
|
|
|
| |
Currently translated at 99.6% (269 of 270 strings)
|
|
|
|
| |
Currently translated at 96.2% (260 of 270 strings)
|
|
|
|
| |
Currently translated at 96.2% (260 of 270 strings)
|
|
|
|
| |
Currently translated at 99.6% (269 of 270 strings)
|
|
|
|
| |
Currently translated at 96.2% (260 of 270 strings)
|
| |
|
|
|
|
| |
This fixes bug 1551
|
|
|
|
|
| |
This was caused by the use the non-threadsafe SharedBuffer in a
threaded context.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
When tunnels entirely above ground were avoided, the
missing pseudorandom calls changed the allowed caves.
Now, above ground tunnels are not placed while
still running all previous pseudorandom calls.
|
| |
|
| |
|
|
|
|
| |
Before players "bounced" too high. Now, while still allowing to bounce, higher speed bounces are throttled.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, sound failed due to errors with hardfp abi build
instructions. As the problem couldn't be found, the softfp
compatible abi was chosen instead.
This move will cause a small performance overhead, but due to the
abi being armeabi-v7a, the internal calculations will still be done
using the FPU.
We also fix some issues with ABI information passing. However, the
fixes aren't sufficient to get sound working.
The patch also fixes an issue with the gitignore file.
|
| |
|
| |
|
|
|
|
|
| |
src/server.cpp
src/emerge.cpp
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Multiplying by a factor of 1/1000.f (rather than dividing by 1000.f) directly
introduces an error of 1 ULP. With this patch, an exact comparison of a
floating point literal with the deserialized F1000 form representing it is now
guaranteed to be successful.
In addition, the maxmium and minimum safely representible floating point
numbers are now well-defined as constants.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Before, android_version.h got changed at every new commit. Now, we
only change it with new minetest releases. Analogous to how cmake
does it, we add an android_version_githash.h file that communicates
the git hash to C++ code.
Also, unify VERS_MAJOR, VERS_MINOR and VERS_PATCH variable
calculation inside the whole makefile.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Speeding up rebuild:
Before, we've written the android_version.h file at every rebuild.
As it thought the file's content has changed, make has rebuilt files
in the source tree that depended on that header file during rebuild,
causing lots of files being rebuilt without there being a reason.
The reasoning of make can be observed by passing -d and V=1 params
to the ndk-build command. You then got logging entries like:
Prerequisite `jni/src/android_version.h' is newer than target `obj/local/armeabi-v7a-hard/objs-debug/minetest/jni/src/areastore.o'.
Preventing race condition build fail:
Before, there was a race condition, where, if the prep_srcdir target
was executed in parallel with the $(ROOT)/jni/src/android_version.h
one, it could happen that the jni/src directory was nonexistent, and
we were trying to write into a file inside. This resulted in a build
failue:
/bin/sh: 1: cannot create [...]/jni/src/android_version.h: Directory nonexistent
Additionally, we now don't remove the link to src/ needlessly anymore.
Keeping this wouldn't have affected the rebuild, but this way its
more proper.
|