Skip to content
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 of Multi-Round-Processing of KSP? #263

Open
bitPogo opened this issue May 8, 2022 · 5 comments
Open

Support of Multi-Round-Processing of KSP? #263

bitPogo opened this issue May 8, 2022 · 5 comments

Comments

@bitPogo
Copy link

bitPogo commented May 8, 2022

Hey,
First of all thank you for maintaining this project - I used it excessively and it is pretty awesome!
However I have just a question in regards to multi-round-processing of KSP with Compiler tests.
Currently I generate some sources which are annotated them self which should be picked up by KSP in subsequent round. While running my Processor in a Compiler Test Context, KSP won't do that, but while running my entire setup in integration it does.
I'm correct if I am assume it has something to do with #129?

@tschuchortdev
Copy link
Owner

I believe that it would fall under the same issue, but I would have to investigate more closely to be sure, since I don't personally use multi-round-processing. It's also possible that this is implemented in the Gradle task, though that would be a bit unusual.

@bitPogo
Copy link
Author

bitPogo commented May 12, 2022

Thanks for the replay! The multi round is actually executed. If it helps I can link you my tests where I am run into this.

@tschuchortdev
Copy link
Owner

Please do, I will take a look at it.

@bitPogo
Copy link
Author

bitPogo commented May 15, 2022

Sry for the late replay, I just wanted to avoid to many parts in the project.
However you may find in test set more information. If I can be of any help please let me know. You should find me in Kotlin Slack via the project name with ease, if you prefer a more direct communication.

@bitPogo
Copy link
Author

bitPogo commented Jul 10, 2022

FYI: It seems like KSP 1.7.0-1.6.0 and KCT 1.4.9. magically resolve that issue (for now).
However I like to wait until the next version of both libs before closing the ticket, since I am not quite sure if this is an intended change or something by accident.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants