-
Notifications
You must be signed in to change notification settings - Fork 240
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
8 Warnings #57
Comments
Xcode does not compile the .metal files for the simulator. You can safely ignore these warnings, since metal code won't run on a simulator. |
@YuAo Is it safe to remove .metal files from Build Phases? |
@YuAo I tried, not, app won't work in this case. |
The stackoverflow solution you provided should work. In the situation of MetalPetal, no code change is required, because MetalPetal loads the metallib file from its own framework bundle. All you need to do is compile the .metal file to a file named "default.metallib" and place it in the MetalPetal.framework bundle. This solution requires that you change your project / build configurations. And everything about Metal Compiler in your project settings won't work anymore because you are not using Xcode's build system to build .metal files. I'm not sure it is a good solution for the framework vendor to implement. I think the proper place for this solution should be the |
I just removed |
Hi! I have 8 warnings like:
no rule to process file '/Frameworks/MetalPetal/Shaders/BlendingShaders.metal' of type 'sourcecode.metal' for architecture 'x86_64' (in target 'MetalPetal')
Could you fix this or provide any suggestions?
The text was updated successfully, but these errors were encountered: