2017-06-07 08:41:11 +00:00
|
|
|
#
|
|
|
|
|
# spec file for package raylib
|
|
|
|
|
#
|
- Update to 3.0.0:
* All global variables from the multiple raylib modules have
been moved to a global context state, it has several benefits, first, better
code readability with more comprehensive variables naming and categorization
(organized by types, i.e. CORE.Window.display.width,
CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows
better memory management to load global context state dynamically when required
(not at the moment), making it easy to implement a hot-reloading mechanism if
desired.
* All memory allocations on raylib and its dependencies now use
RL_MALLOC, RL_FREE and similar macros. Now users can easely hook their own
memory allocations mechanism if desired, having more control over memory
allocated internally by the library. Additionally, it makes it easier to port
the library to embedded devices where memory control is critical. For more info
check raylib issue #1074.
* All I/O file accesses from raylib are being moved
to memory data access, now all I/O file access is centralized into just four
functions: LoadFileData(), SaveFileData(), LoadFileText(), SaveFileText().
Users can just update those functions to any I/O file system. This change makes
it easier to integrate raylib with Virtual File Systems or custom I/O file
implementations.
* All raylib data structures have been reviewed and optimized
for pass-by-value usage. One of raylib distinctive design decisions is that
most of its functions receive and return data by value. This design makes
raylib really simple for newcomers, avoiding pointers and allowing complete
access to all structures data in a simple way. The downside is that data is
copied on stack every function call and that copy could be costly so, all
raylib data structures have been optimized to stay under 64 bytes for fast copy
and retrieve.
* All raylib tracelog messages have been reviewd and categorized
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=20
2020-03-31 09:29:16 +00:00
|
|
|
# Copyright (c) 2020 SUSE LLC
|
2017-06-07 08:41:11 +00:00
|
|
|
#
|
|
|
|
|
# All modifications and additions to the file contributed by third parties
|
|
|
|
|
# remain the property of their copyright owners, unless otherwise agreed
|
|
|
|
|
# upon. The license for this file, and modifications and additions to the
|
|
|
|
|
# file, is the same license as for the pristine package itself (unless the
|
|
|
|
|
# license for the pristine package is not an Open Source License, in which
|
|
|
|
|
# case the license is the MIT License). An "Open Source License" is a
|
|
|
|
|
# license that conforms to the Open Source Definition (Version 1.9)
|
|
|
|
|
# published by the Open Source Initiative.
|
|
|
|
|
|
- Update to 3.0.0:
* All global variables from the multiple raylib modules have
been moved to a global context state, it has several benefits, first, better
code readability with more comprehensive variables naming and categorization
(organized by types, i.e. CORE.Window.display.width,
CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows
better memory management to load global context state dynamically when required
(not at the moment), making it easy to implement a hot-reloading mechanism if
desired.
* All memory allocations on raylib and its dependencies now use
RL_MALLOC, RL_FREE and similar macros. Now users can easely hook their own
memory allocations mechanism if desired, having more control over memory
allocated internally by the library. Additionally, it makes it easier to port
the library to embedded devices where memory control is critical. For more info
check raylib issue #1074.
* All I/O file accesses from raylib are being moved
to memory data access, now all I/O file access is centralized into just four
functions: LoadFileData(), SaveFileData(), LoadFileText(), SaveFileText().
Users can just update those functions to any I/O file system. This change makes
it easier to integrate raylib with Virtual File Systems or custom I/O file
implementations.
* All raylib data structures have been reviewed and optimized
for pass-by-value usage. One of raylib distinctive design decisions is that
most of its functions receive and return data by value. This design makes
raylib really simple for newcomers, avoiding pointers and allowing complete
access to all structures data in a simple way. The downside is that data is
copied on stack every function call and that copy could be costly so, all
raylib data structures have been optimized to stay under 64 bytes for fast copy
and retrieve.
* All raylib tracelog messages have been reviewd and categorized
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=20
2020-03-31 09:29:16 +00:00
|
|
|
# Please submit bugfixes or comments via https://bugs.opensuse.org/
|
2017-06-07 08:41:11 +00:00
|
|
|
#
|
|
|
|
|
|
2017-06-08 15:26:37 +00:00
|
|
|
|
2017-06-07 08:41:11 +00:00
|
|
|
Name: raylib
|
- Update to 3.0.0:
* All global variables from the multiple raylib modules have
been moved to a global context state, it has several benefits, first, better
code readability with more comprehensive variables naming and categorization
(organized by types, i.e. CORE.Window.display.width,
CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows
better memory management to load global context state dynamically when required
(not at the moment), making it easy to implement a hot-reloading mechanism if
desired.
* All memory allocations on raylib and its dependencies now use
RL_MALLOC, RL_FREE and similar macros. Now users can easely hook their own
memory allocations mechanism if desired, having more control over memory
allocated internally by the library. Additionally, it makes it easier to port
the library to embedded devices where memory control is critical. For more info
check raylib issue #1074.
* All I/O file accesses from raylib are being moved
to memory data access, now all I/O file access is centralized into just four
functions: LoadFileData(), SaveFileData(), LoadFileText(), SaveFileText().
Users can just update those functions to any I/O file system. This change makes
it easier to integrate raylib with Virtual File Systems or custom I/O file
implementations.
* All raylib data structures have been reviewed and optimized
for pass-by-value usage. One of raylib distinctive design decisions is that
most of its functions receive and return data by value. This design makes
raylib really simple for newcomers, avoiding pointers and allowing complete
access to all structures data in a simple way. The downside is that data is
copied on stack every function call and that copy could be costly so, all
raylib data structures have been optimized to stay under 64 bytes for fast copy
and retrieve.
* All raylib tracelog messages have been reviewd and categorized
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=20
2020-03-31 09:29:16 +00:00
|
|
|
Version: 3.0.0
|
2017-06-07 08:41:11 +00:00
|
|
|
Release: 0
|
2017-11-03 12:17:22 +00:00
|
|
|
Summary: C library for learning video game programming
|
2017-06-07 08:41:11 +00:00
|
|
|
License: Zlib
|
2017-06-08 15:26:37 +00:00
|
|
|
Group: Development/Libraries/C and C++
|
Accepting request 706634 from home:jubalh:branches:devel:libraries:c_c++
- Update to 2.5.0:
* New window management and filesystem functions to query monitor
information, deal with clipboard, check directory files info and
even launch a URL with default system web browser. Experimental
High-DPI monitor support has also been added through a compile flag.
* Redesigned Gamepad mechanism, now generic for all platforms and
gamepads, no more specific gamepad configurations.
* Redesigned UWP input system, now raylib supports UWP seamlessly,
previous implementation required a custom input system implemented
in user code.
* rlgl module has been redesigned to support a unique buffer for
shapes drawing batching, including LINES, TRIANGLES, QUADS in the
same indexed buffer, also added support for multi-buffering if required.
Additionally, rlPushMatrix()/rlPopMatrix() functionality has been
reviewed to behave exactly like OpenGL 1.1, models_rlgl_solar_system
example has been added to illustrate this behaviour.
* VR simulator has been reviewed to allow custom configuration of
Head-Mounted-Device parameters and distortion shader, core_vr_simulator
has been properly adapted to showcase this new functionality, now
the VR simulator is a generic configurable stereo rendering system
that allows any VR device simulation with just a few lines of code
or even dynamic tweaking of HMD parameters.
* Support for Unicode text drawing; now raylib processes UTF8
strings on drawing, supporting Unicode codepoints, allowing rendering
mostly any existent language (as long as the font with the glyphs is provided).
* Brand new text management API, with the addition of multiple functions
to deal with string data
* Multiple new shapes and textures drawing functions
* Experimental cubemap support, to automatically load multiple
cubemap layouts (LoadTextureCubemap()).
OBS-URL: https://build.opensuse.org/request/show/706634
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=18
2019-05-31 09:30:54 +00:00
|
|
|
URL: http://www.raylib.com
|
2018-07-24 09:17:02 +00:00
|
|
|
Source: https://github.com/raysan5/raylib/archive/%{version}.tar.gz
|
2017-06-07 08:41:11 +00:00
|
|
|
BuildRequires: Mesa-libGL-devel
|
2018-07-24 09:29:32 +00:00
|
|
|
BuildRequires: cmake
|
2018-05-18 17:44:43 +00:00
|
|
|
BuildRequires: gcc-c++
|
2018-07-24 09:29:32 +00:00
|
|
|
BuildRequires: libXcursor-devel
|
2018-05-18 17:44:43 +00:00
|
|
|
BuildRequires: libXi-devel
|
2018-07-24 09:29:32 +00:00
|
|
|
BuildRequires: libXinerama-devel
|
|
|
|
|
BuildRequires: libXrandr-devel
|
2017-06-07 08:41:11 +00:00
|
|
|
|
|
|
|
|
%description
|
2017-11-03 12:17:22 +00:00
|
|
|
A C library for learning video game programming.
|
|
|
|
|
raylib is inspired by the Borland BGI graphics library and by the XNA framework.
|
2017-06-07 08:41:11 +00:00
|
|
|
|
|
|
|
|
%package -n raylib-devel
|
|
|
|
|
Summary: Development files for %{name}
|
2017-06-08 15:26:37 +00:00
|
|
|
Group: Development/Libraries/C and C++
|
- Update to 3.0.0:
* All global variables from the multiple raylib modules have
been moved to a global context state, it has several benefits, first, better
code readability with more comprehensive variables naming and categorization
(organized by types, i.e. CORE.Window.display.width,
CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows
better memory management to load global context state dynamically when required
(not at the moment), making it easy to implement a hot-reloading mechanism if
desired.
* All memory allocations on raylib and its dependencies now use
RL_MALLOC, RL_FREE and similar macros. Now users can easely hook their own
memory allocations mechanism if desired, having more control over memory
allocated internally by the library. Additionally, it makes it easier to port
the library to embedded devices where memory control is critical. For more info
check raylib issue #1074.
* All I/O file accesses from raylib are being moved
to memory data access, now all I/O file access is centralized into just four
functions: LoadFileData(), SaveFileData(), LoadFileText(), SaveFileText().
Users can just update those functions to any I/O file system. This change makes
it easier to integrate raylib with Virtual File Systems or custom I/O file
implementations.
* All raylib data structures have been reviewed and optimized
for pass-by-value usage. One of raylib distinctive design decisions is that
most of its functions receive and return data by value. This design makes
raylib really simple for newcomers, avoiding pointers and allowing complete
access to all structures data in a simple way. The downside is that data is
copied on stack every function call and that copy could be costly so, all
raylib data structures have been optimized to stay under 64 bytes for fast copy
and retrieve.
* All raylib tracelog messages have been reviewd and categorized
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=20
2020-03-31 09:29:16 +00:00
|
|
|
Requires: libraylib301 = %{version}
|
2017-06-07 08:41:11 +00:00
|
|
|
Requires: openal-soft-devel
|
|
|
|
|
|
|
|
|
|
%description -n raylib-devel
|
2017-11-03 12:17:22 +00:00
|
|
|
Development files and headers for %{name}.
|
2017-06-07 08:41:11 +00:00
|
|
|
|
- Update to 3.0.0:
* All global variables from the multiple raylib modules have
been moved to a global context state, it has several benefits, first, better
code readability with more comprehensive variables naming and categorization
(organized by types, i.e. CORE.Window.display.width,
CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows
better memory management to load global context state dynamically when required
(not at the moment), making it easy to implement a hot-reloading mechanism if
desired.
* All memory allocations on raylib and its dependencies now use
RL_MALLOC, RL_FREE and similar macros. Now users can easely hook their own
memory allocations mechanism if desired, having more control over memory
allocated internally by the library. Additionally, it makes it easier to port
the library to embedded devices where memory control is critical. For more info
check raylib issue #1074.
* All I/O file accesses from raylib are being moved
to memory data access, now all I/O file access is centralized into just four
functions: LoadFileData(), SaveFileData(), LoadFileText(), SaveFileText().
Users can just update those functions to any I/O file system. This change makes
it easier to integrate raylib with Virtual File Systems or custom I/O file
implementations.
* All raylib data structures have been reviewed and optimized
for pass-by-value usage. One of raylib distinctive design decisions is that
most of its functions receive and return data by value. This design makes
raylib really simple for newcomers, avoiding pointers and allowing complete
access to all structures data in a simple way. The downside is that data is
copied on stack every function call and that copy could be costly so, all
raylib data structures have been optimized to stay under 64 bytes for fast copy
and retrieve.
* All raylib tracelog messages have been reviewd and categorized
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=20
2020-03-31 09:29:16 +00:00
|
|
|
%package -n libraylib301
|
2017-11-03 12:17:22 +00:00
|
|
|
Summary: C library for learning video game programming
|
2017-09-08 16:41:13 +00:00
|
|
|
Group: System/Libraries
|
2017-06-08 15:26:37 +00:00
|
|
|
|
- Update to 3.0.0:
* All global variables from the multiple raylib modules have
been moved to a global context state, it has several benefits, first, better
code readability with more comprehensive variables naming and categorization
(organized by types, i.e. CORE.Window.display.width,
CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows
better memory management to load global context state dynamically when required
(not at the moment), making it easy to implement a hot-reloading mechanism if
desired.
* All memory allocations on raylib and its dependencies now use
RL_MALLOC, RL_FREE and similar macros. Now users can easely hook their own
memory allocations mechanism if desired, having more control over memory
allocated internally by the library. Additionally, it makes it easier to port
the library to embedded devices where memory control is critical. For more info
check raylib issue #1074.
* All I/O file accesses from raylib are being moved
to memory data access, now all I/O file access is centralized into just four
functions: LoadFileData(), SaveFileData(), LoadFileText(), SaveFileText().
Users can just update those functions to any I/O file system. This change makes
it easier to integrate raylib with Virtual File Systems or custom I/O file
implementations.
* All raylib data structures have been reviewed and optimized
for pass-by-value usage. One of raylib distinctive design decisions is that
most of its functions receive and return data by value. This design makes
raylib really simple for newcomers, avoiding pointers and allowing complete
access to all structures data in a simple way. The downside is that data is
copied on stack every function call and that copy could be costly so, all
raylib data structures have been optimized to stay under 64 bytes for fast copy
and retrieve.
* All raylib tracelog messages have been reviewd and categorized
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=20
2020-03-31 09:29:16 +00:00
|
|
|
%description -n libraylib301
|
2017-11-03 12:17:22 +00:00
|
|
|
A C library for learning video game programming.
|
2017-06-08 15:26:37 +00:00
|
|
|
|
2017-06-07 08:41:11 +00:00
|
|
|
%prep
|
- Update to 3.0.0:
* All global variables from the multiple raylib modules have
been moved to a global context state, it has several benefits, first, better
code readability with more comprehensive variables naming and categorization
(organized by types, i.e. CORE.Window.display.width,
CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows
better memory management to load global context state dynamically when required
(not at the moment), making it easy to implement a hot-reloading mechanism if
desired.
* All memory allocations on raylib and its dependencies now use
RL_MALLOC, RL_FREE and similar macros. Now users can easely hook their own
memory allocations mechanism if desired, having more control over memory
allocated internally by the library. Additionally, it makes it easier to port
the library to embedded devices where memory control is critical. For more info
check raylib issue #1074.
* All I/O file accesses from raylib are being moved
to memory data access, now all I/O file access is centralized into just four
functions: LoadFileData(), SaveFileData(), LoadFileText(), SaveFileText().
Users can just update those functions to any I/O file system. This change makes
it easier to integrate raylib with Virtual File Systems or custom I/O file
implementations.
* All raylib data structures have been reviewed and optimized
for pass-by-value usage. One of raylib distinctive design decisions is that
most of its functions receive and return data by value. This design makes
raylib really simple for newcomers, avoiding pointers and allowing complete
access to all structures data in a simple way. The downside is that data is
copied on stack every function call and that copy could be costly so, all
raylib data structures have been optimized to stay under 64 bytes for fast copy
and retrieve.
* All raylib tracelog messages have been reviewd and categorized
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=20
2020-03-31 09:29:16 +00:00
|
|
|
%setup -q -n raylib-3.0.0
|
2017-06-07 08:41:11 +00:00
|
|
|
|
|
|
|
|
%build
|
2018-05-18 17:44:43 +00:00
|
|
|
%cmake \
|
2018-07-24 09:17:02 +00:00
|
|
|
-DPLATFORM=Desktop \
|
|
|
|
|
-DSHARED=ON
|
2017-06-07 08:41:11 +00:00
|
|
|
|
|
|
|
|
%install
|
2018-05-18 17:44:43 +00:00
|
|
|
%cmake_install
|
2017-06-08 15:26:37 +00:00
|
|
|
|
- Update to 3.0.0:
* All global variables from the multiple raylib modules have
been moved to a global context state, it has several benefits, first, better
code readability with more comprehensive variables naming and categorization
(organized by types, i.e. CORE.Window.display.width,
CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows
better memory management to load global context state dynamically when required
(not at the moment), making it easy to implement a hot-reloading mechanism if
desired.
* All memory allocations on raylib and its dependencies now use
RL_MALLOC, RL_FREE and similar macros. Now users can easely hook their own
memory allocations mechanism if desired, having more control over memory
allocated internally by the library. Additionally, it makes it easier to port
the library to embedded devices where memory control is critical. For more info
check raylib issue #1074.
* All I/O file accesses from raylib are being moved
to memory data access, now all I/O file access is centralized into just four
functions: LoadFileData(), SaveFileData(), LoadFileText(), SaveFileText().
Users can just update those functions to any I/O file system. This change makes
it easier to integrate raylib with Virtual File Systems or custom I/O file
implementations.
* All raylib data structures have been reviewed and optimized
for pass-by-value usage. One of raylib distinctive design decisions is that
most of its functions receive and return data by value. This design makes
raylib really simple for newcomers, avoiding pointers and allowing complete
access to all structures data in a simple way. The downside is that data is
copied on stack every function call and that copy could be costly so, all
raylib data structures have been optimized to stay under 64 bytes for fast copy
and retrieve.
* All raylib tracelog messages have been reviewd and categorized
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=20
2020-03-31 09:29:16 +00:00
|
|
|
%post -n libraylib301 -p /sbin/ldconfig
|
|
|
|
|
%postun -n libraylib301 -p /sbin/ldconfig
|
2017-06-08 15:26:37 +00:00
|
|
|
|
- Update to 3.0.0:
* All global variables from the multiple raylib modules have
been moved to a global context state, it has several benefits, first, better
code readability with more comprehensive variables naming and categorization
(organized by types, i.e. CORE.Window.display.width,
CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows
better memory management to load global context state dynamically when required
(not at the moment), making it easy to implement a hot-reloading mechanism if
desired.
* All memory allocations on raylib and its dependencies now use
RL_MALLOC, RL_FREE and similar macros. Now users can easely hook their own
memory allocations mechanism if desired, having more control over memory
allocated internally by the library. Additionally, it makes it easier to port
the library to embedded devices where memory control is critical. For more info
check raylib issue #1074.
* All I/O file accesses from raylib are being moved
to memory data access, now all I/O file access is centralized into just four
functions: LoadFileData(), SaveFileData(), LoadFileText(), SaveFileText().
Users can just update those functions to any I/O file system. This change makes
it easier to integrate raylib with Virtual File Systems or custom I/O file
implementations.
* All raylib data structures have been reviewed and optimized
for pass-by-value usage. One of raylib distinctive design decisions is that
most of its functions receive and return data by value. This design makes
raylib really simple for newcomers, avoiding pointers and allowing complete
access to all structures data in a simple way. The downside is that data is
copied on stack every function call and that copy could be costly so, all
raylib data structures have been optimized to stay under 64 bytes for fast copy
and retrieve.
* All raylib tracelog messages have been reviewd and categorized
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=20
2020-03-31 09:29:16 +00:00
|
|
|
%files -n libraylib301
|
|
|
|
|
%{_libdir}/libraylib.so.301
|
|
|
|
|
%{_libdir}/libraylib.so.3.0.0
|
2017-06-07 08:41:11 +00:00
|
|
|
|
|
|
|
|
%files -n raylib-devel
|
- Update to 3.0.0:
* All global variables from the multiple raylib modules have
been moved to a global context state, it has several benefits, first, better
code readability with more comprehensive variables naming and categorization
(organized by types, i.e. CORE.Window.display.width,
CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows
better memory management to load global context state dynamically when required
(not at the moment), making it easy to implement a hot-reloading mechanism if
desired.
* All memory allocations on raylib and its dependencies now use
RL_MALLOC, RL_FREE and similar macros. Now users can easely hook their own
memory allocations mechanism if desired, having more control over memory
allocated internally by the library. Additionally, it makes it easier to port
the library to embedded devices where memory control is critical. For more info
check raylib issue #1074.
* All I/O file accesses from raylib are being moved
to memory data access, now all I/O file access is centralized into just four
functions: LoadFileData(), SaveFileData(), LoadFileText(), SaveFileText().
Users can just update those functions to any I/O file system. This change makes
it easier to integrate raylib with Virtual File Systems or custom I/O file
implementations.
* All raylib data structures have been reviewed and optimized
for pass-by-value usage. One of raylib distinctive design decisions is that
most of its functions receive and return data by value. This design makes
raylib really simple for newcomers, avoiding pointers and allowing complete
access to all structures data in a simple way. The downside is that data is
copied on stack every function call and that copy could be costly so, all
raylib data structures have been optimized to stay under 64 bytes for fast copy
and retrieve.
* All raylib tracelog messages have been reviewd and categorized
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=20
2020-03-31 09:29:16 +00:00
|
|
|
%license LICENSE
|
2018-05-18 17:44:43 +00:00
|
|
|
%doc CHANGELOG README.md
|
2017-06-07 08:41:11 +00:00
|
|
|
%{_includedir}/raylib.h
|
|
|
|
|
%{_libdir}/libraylib.so
|
2018-05-18 17:44:43 +00:00
|
|
|
%{_libdir}/pkgconfig/raylib.pc
|
Accepting request 706634 from home:jubalh:branches:devel:libraries:c_c++
- Update to 2.5.0:
* New window management and filesystem functions to query monitor
information, deal with clipboard, check directory files info and
even launch a URL with default system web browser. Experimental
High-DPI monitor support has also been added through a compile flag.
* Redesigned Gamepad mechanism, now generic for all platforms and
gamepads, no more specific gamepad configurations.
* Redesigned UWP input system, now raylib supports UWP seamlessly,
previous implementation required a custom input system implemented
in user code.
* rlgl module has been redesigned to support a unique buffer for
shapes drawing batching, including LINES, TRIANGLES, QUADS in the
same indexed buffer, also added support for multi-buffering if required.
Additionally, rlPushMatrix()/rlPopMatrix() functionality has been
reviewed to behave exactly like OpenGL 1.1, models_rlgl_solar_system
example has been added to illustrate this behaviour.
* VR simulator has been reviewed to allow custom configuration of
Head-Mounted-Device parameters and distortion shader, core_vr_simulator
has been properly adapted to showcase this new functionality, now
the VR simulator is a generic configurable stereo rendering system
that allows any VR device simulation with just a few lines of code
or even dynamic tweaking of HMD parameters.
* Support for Unicode text drawing; now raylib processes UTF8
strings on drawing, supporting Unicode codepoints, allowing rendering
mostly any existent language (as long as the font with the glyphs is provided).
* Brand new text management API, with the addition of multiple functions
to deal with string data
* Multiple new shapes and textures drawing functions
* Experimental cubemap support, to automatically load multiple
cubemap layouts (LoadTextureCubemap()).
OBS-URL: https://build.opensuse.org/request/show/706634
OBS-URL: https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib?expand=0&rev=18
2019-05-31 09:30:54 +00:00
|
|
|
%{_libdir}/cmake/raylib/
|
2017-06-07 08:41:11 +00:00
|
|
|
|
|
|
|
|
%changelog
|
