| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Fixes: c3b948b1 ("Replaced skybox HDR image")
|
|
|
|
|
|
|
|
|
|
|
|
Replaced old dwarf model
|
|
|
|
Note that HDR exposured possibilities are not used on this example...
|
|
Replaced by medieval 3d assets
|
|
|
|
It seems TCC was not casting correctly int values to float in some
specific situations
|
|
src/core.c does explicitly skip including <camera.h> on Android
and tests fail. Therefore skip these failing tests.
Closes #507.
|
|
|
|
Currently, if:
* GCC doesn't supports -no-pie: Build error
* GCC supports -no-pie
* GCC is not configured with --enable-default-pie: No-op
* GCC is configured with --enable-default-pie:
Slightly worse performance because we still generate -fpie code
(-pie affects linker, -fpie affects compiler)
So instead of probing for existence of -fno-pie -no-pie, remove it altogether.
Fixes #540: Build breakage on Debian 8 with gcc 4.9.
|
|
|
|
Review raylib_icon resource
|
|
|
|
- Preparing MP3 files support
- Jumped version to raylib 2.0-dev (too many breaking changes...)
|
|
- Renamed Begin3dMode() --> BeginMode3D()
- Renamed Begin2dMode() --> BeginMode2D()
- Renamed End3dMode() --> EndMode3D()
- Renamed End2dMode() --> EndMode2D()
|
|
- Some examples tweaks
- Reviewed ImageFormat()
- Use float for text fontSize
|
|
Just added a fallback in the meantime...
|
|
- Added Vector3OrthoNormalize() to raymath.h - not sure if it is correct
- Implemented MeshBinormals() - Mesh struct has not a place for them...
- Updated model_material_pbr example - tested but not working on my GPU
(old Intel HD), actually, it never worked on it...
|
|
|
|
|
|
|
|
Fix potential bugs from static analysis
|
|
|
|
|
|
|
|
|
|
|
|
Changes made based on commentary in pull request 513
|
|
|
|
raymath.h: Use C99 inline semantics
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Renamed function for consistency with a possible Mesh manipulation functions (maybe added in a future). Naming follows Image*() manipulation functions.
|
|
RAYMATH_EXTERN_INLINE was renamed to RAYMATH_HEADER_ONLY, which user code
may define if they want to use it as header-only library. If multiple
files in the same project define RAYMATH_HEADER_ONLY, they might each
have duplicate out-of-line definitions of the same functions.
By default, raymath.h exposes inline definitions, which instructs the
compiler _not_ to generate out-of-line definitons, if out-of-line
definitions are required, those of the file defined with
RAYLIB_IMPLEMENTATION are used instead. There may be only one such file.
In C++ mode, the compiler will select only one out-of-line definition
automatically, so no need to define a RAYLIB_IMPLEMENTATION.
Unfortunately, we have to remove raymath function declaration from
raylib.h as those declarations would lead to duplicate out-of-line
definitions which would yield linker errors. This problem didn't
exist with GNU89 or C++, because there multiple defintions are ok,
but in C99 they aren't.
|
|
|
|
This reverts commit 6ffc8cb7990fb4ff40f205cb53bec797b10e48a2.
and commit e4d7bbec1ef08279495ac41f5f8c4be359c58cf0.
which I pushed by mistake...
|
|
RAYMATH_EXTERN_INLINE was renamed to RAYMATH_HEADER_ONLY, which user code
may define if they want to use it as header-only library. If multiple
files in the same project define RAYMATH_HEADER_ONLY, they might each
have duplicate out-of-line definitions of the same functions.
By default, raymath.h exposes inline definitions, which instructs the
compiler _not_ to generate out-of-line definitons, if out-of-line
definitions are required, those of the file defined with
RAYLIB_IMPLEMENTATION are used instead. There may be only one such file.
In C++ mode, the compiler will select only one out-of-line definition
automatically, so no need to define a RAYLIB_IMPLEMENTATION.
Unfortunately, we have to remove raymath function declaration from
raylib.h as those declarations would lead to duplicate out-of-line
definitions which would yield linker errors. This problem didn't
exist with GNU89 or C++, because there multiple defintions are ok,
but in C99 they aren't.
|
|
|
