-
Notifications
You must be signed in to change notification settings - Fork 19
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
BUG: MacOS support libraries end up into res://build/*
#52
Comments
Making the link arguments more explicit we are building into the Godot dir but grab the sub libraries from the
So what would happen when building local then copy into |
Some more info about dynlib https://lessons.livecode.com/m/4071/l/15029-linking-an-osx-external-bundle-with-a-dylib-library
and
|
We can run the same on Godot
|
So in short
helps a little for understanding and
shows ways to fix stuff hopefully. |
Remarks
this is the wrong answer as it probably should be relative to the project root
This is not working ... it should be in an application context I guess? |
Export gameIf I export the game to MacOS App we get (too few files but what can we do here)
Check path
Change pathInvalidates signature so that is not how should be done
Recheck pathName is not changed ... arg
ARM64?
Wot?!? |
After #33 lands we still face:
The MacOS build process results in the supporting files into
res://build/
directory.Fiddling removing
/build
makes them required inres://
aka the root of the demo project. Which is worse.and the other(s) too
We do not understand this dynamics on MacOS. Help needed.
The text was updated successfully, but these errors were encountered: