-
Notifications
You must be signed in to change notification settings - Fork 510
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
Support for "compressed" .framework references to avoid corruption #11671
Comments
This is actually NuGet issue so maybe https://github.com/NuGet/Home would be better fit? |
Agreed. Any workaround will have non negligible impact on build performance. |
Adding a link to that: NuGet/Home#10893 But I don't think this is a nuget issue. Since this is really an issue with the Windows OS not supporting symbolic links properly, the SDK will have to handle this. |
Adding a link to another, more generic issue: NuGet/Home#10734 |
Recently there was an XML file added to UNIX-like permission could be kept properly. |
We need to verify if macOS (and Catalyst) support [0] the newer "user framework" format that is used by iOS, tvOS and watchOS. Those frameworks are not using symlinks (since they do not have to care about versioning). If this is supported then the frameworks could be converted to this format - and that would solve the issue. [0] build time, run time and submissions to App Store |
This has been implemented, we'll automatically zip up any (xc)frameworks with symlinks now. |
Steps to Reproduce
Expected Behavior
The framework does not get corrupted.
Another part of the system is that I have to build this framework on macOS, but then I have to build more things on Windows and eventually run a nuget pack on Windows. This means, the framework has to survive uploading and copying on Windows. For example, I noticed that DevOps uploads the framework, but duplicates the files. As a result, this needs to be compressed (by me maybe) on a macOS agent, and then just reference that.
Actual Behavior
The compression of a NuGet uses a compression system that does not preserve symbolic links, causing compiler failures.
Environment
.NET 6
Build Logs
Example Project (If Possible)
The text was updated successfully, but these errors were encountered: