-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Update "Tips for improving Kotlin/Native compilation times" #4575
Conversation
> | ||
{style="note"} | ||
|
||
To build a platform-specific framework, call the `embedAndSignAppleFrameworkForXcode` task. |
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.
Could you please cross reference the embedAndSign guide
Release is highly optimized, and this takes a lot of time: compilation of release binaries takes an order of magnitude | ||
more time than debug binaries. In a typical development cycle, all the optimizations might be unnecessary. So, if | ||
your development cycle uses a task with "Release" in its name, consider replacing it with "Debug". Similarly, instead | ||
of running `assembleXCFramework`, you can run `assembleXcfDebugXCFramework`, for example. |
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.
assembleXcfDebugXCFramework
nit: I think the task is likely to be called assembleSharedDebugXCFramework
or assembleComposeAppDebugXCFramework
since we use project name as the default XCFramework name (same as the framework's baseName)
This task is obsolete and superseded with `embedAndSignAppleFrameworkForXcode`.
dSYMs are generated for release frameworks as well as for debug ones.
39d6d1d
to
dc251d5
Compare
This PR adds a few more tips to the document, clarifies existing tips and removes an outdated part.