-
Notifications
You must be signed in to change notification settings - Fork 285
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 generated JVM bytecode #95
Comments
Put up a prototype to test with here: ZacSweers/MoshiX#43 |
Fixed in #138. |
I don't think this is resolved. I updated my bytecode generation branch linked above, and while the classes themselves do get generated, they don't link at compile-time
|
* Report KSP logs in compilations Resolves google#69. This is based on an implementation I've been using in my projects, and also works around internal access across modules via lesser-known suppression mechanism until kotlin finally finishes implementing friend-paths support in their gradle/IDE tooling. * Add tests * Remove unnecessary copy of MessageCollectorBasedKSPLogger Co-authored-by: Thilo Schuchort <[email protected]>
Trying to revisit this in github.com/square/moshi and finding the above remains an issue. I'm also finding that KSP2 completely doesn't link generated code against class files, let alone class files against source files. |
Reference where I've been working on this square/moshi#1858. You can reproduce it there by running the |
While KSP doesn't have any facility to support generating bytecode, it should pick up bytecode generated solely by processors and add them to compile classpath, so as to participate in later compilation.
The text was updated successfully, but these errors were encountered: