Closed icrc-fdeniger closed 2 months ago
Thanks for raising this @icrc-fdeniger
I think I know why ksp works and kapt does not. The overhead of kapt's stub generation process likely ran into permission problems in your non-admin setup. The exact folders it tried to write to are unknown, but they were probably system-protected. Ksp, on the other hand, directly processes kotlin symbols removing the need for stub generation entirely, perhaps bypassing the troublesome permission issues.
See more in Why KSP? Also Android documentation recommends to migrate to ksp!
This seems to be a valid change and I think ksp is safe for room compiler. Would you like to submit a PR for this ?
Sure I tried with a first draft here :) https://github.com/google/android-fhir/pull/2471
Not an expert with KSP, KAPT so I'm sure it should be polished. it's ok for me with this configuration but I will need to have feedbacks on this. For instance for the ksp version (1.9.21-1.0.16). It seems it was the only config working for me.. but I can do more tests
Thanks and no worries @icrc-fdeniger. Have left some comments on your PR.
Describe the bug can't start the demo application on Windows 10 with java 17
Relevant log:
I managed to let it work by migrating to kspid("com.google.devtools.ksp").version("1.9.21-1.0.16"): https://github.com/google/android-fhir/compare/master...icrc-fdeniger:android-fhir:icrc-ok-pull-data?expand=1#diff-84cb3f8fc96e6909e77e32e7f45a90496814fd34fb2e9822056aea55aaa0e9e7
I believe the root is that I can open a file located the folder C:\WINDOWS ( not an admin)