-
Notifications
You must be signed in to change notification settings - Fork 398
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
fix reference to macos.mm #1953
Conversation
Apparently geting alignment right pre-C++17 is not easy. Well, 2^32 fits entirely in Lua "double" 2^53 so it's fine to assume alignment of 1. Fixes #1916.
VS2013 doesn't support them.
When a fused löve executable is signed with codesign on Windows some data is appended to the executable, preventing physfs from finding the zip file at the end of the file. To help physfs out a bit, we try to find the zip ourselves in the case of regular mount failure by looking for it's characteristic end of central directory record and, once found, pretend to physfs that the file is shorter than it actually is and ends at the end of the zip file.
On 32-bit platforms, full-lightuserdata is always supported since their pointer fits entirely in 2^48 limitation that LuaJIT had in older version. Also suppress warning about key > 0x20000000000000ULL is always false on enet.cpp when compiling on 32-bit platforms.
Fixes #1880.
Add PHYSFS_Io StripSuffixIo to skip codesign signatures
Hash function fixes.
…sult if it's not there already.
…replacing an existing binding. issue #1936.
Fix #1943 - Duplicate frames being skipped when decoding Theora
Clamp the mouse coordinates to the window's dimensions.
@@ -328,7 +328,7 @@ set(LOVE_SRC_COMMON | |||
|
|||
if (APPLE) | |||
set(LOVE_SRC_COMMON ${LOVE_SRC_COMMON} | |||
src/common/macosx.mm | |||
src/common/macos.mm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file is still macosx.mm
in the main branch, it's only renamed to macos.mm
in 12.0-development
. Did you mean to make the PR based against that branch instead of main
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I did. Sorry for the inconvenience.
No description provided.