Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[raylib] update to 2.5.0 #7848

Merged
merged 1 commit into from
Sep 3, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ports/raylib/CONTROL
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
Source: raylib
Version: 2019-04-27-2
Version: 2.5.0
Description: A simple and easy-to-use library to enjoy videogames programming
#Build-Depends: glfw3

Expand Down
4 changes: 2 additions & 2 deletions ports/raylib/portfile.cmake
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,8 @@ include(vcpkg_common_functions)
vcpkg_from_github(
OUT_SOURCE_PATH SOURCE_PATH
REPO raysan5/raylib
REF f37e55a77bd6177dbaea4d7f484961c09104e104
SHA512 57146ebc7ab22a4e60c1d9eecd4c7a8f1930d6709f45761af809da9ea4f161e9fd450fa1042252a80bd7952ed9571a5d8dee4d454c8903a778e3e1328300b2bd
REF a9f33c9a8962735fed5dd1857709d159bc4056fc # 2.5.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just write 2.5.0 honestly I would be fine if you just updated to the HEAD of master.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cbezault see issue #7835,user need update to 2.5 (not 2.5-dev!).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Author of raylib says 2.5-dev is REALLY outdated compared to the 2.5 release, so the file itself needs to be updated

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm OK with having the commit ID instead of the release tag. We have had problems with release tags changing the tagged commit and invalidating our SHA512.

SHA512 36ee474d5f1791385a6841e20632e078c0d3a591076faed0a648533513a3218e2817b0bbf7a921cc003c9aaf6a07024fd48830697d9d85eba307be27bd884ad8
HEAD_REF master
)

Expand Down