-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
[4.0] Add GDNative Framework support for macOS, add Unix symlink API. #46866
[4.0] Add GDNative Framework support for macOS, add Unix symlink API. #46866
Conversation
080d4a3
to
bedb40c
Compare
Actually, just renaming |
90d316a
to
c06afe8
Compare
Removed separate |
I guess we'll need to clarify the documentation so users know they can put either a universal binary, an x86_64 or an arm64 binary for the single |
c06afe8
to
a1cb6f0
Compare
Thanks! |
Adds ability to select, load and export (both
.dmg
and.zip
) macOS ".frameworks" as GDNative libraries.Adds minimal symlink API to
DirAccess
(frameworks usually contain multiple relative symlinks).Framework export won't work from Windows (If there are symlinks in the framework). NTFS have support for symlinks, but I do not see any way to get relative symlink target path, all functions seems to return full path. And creating symlinks seems to require privilege elevation. Not sure what to do with it (currently it will print a warning).
Edit: Relative symlinks are supported and
DeviceIoControl(FSCTL_GET_REPARSE_POINT)
function can get correct relative path, but none of Windows apps seems to use them and all Windows ZIP software extract symlinks as text files with the target path. Even if workingreadlink
equivalent is added, Windows users won't be able to acquire macOS framework with correct structure in the first place.Version for 3.2 - #46860