-
Notifications
You must be signed in to change notification settings - Fork 98
Add linuxMain source set #2007
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
Add linuxMain source set #2007
Conversation
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.
It seems it's not required change, but "convenience" util
We're working on to align buildSrc
with AOSP (ETA is not clear now), so I'd avoid such not-necessary changes there to avoid future merge complications
@MatkovIvan The Linux compose PR needs to add many code to a linuxMain source set (as code is shared between linux x64 and arm64). So I opened this PR to add it. Please suggest how to do this without touching buildSrc. I am not sure it would be better to add this to every build.gradle. |
|
Ok, I will do that instead as you prefer. |
I guess it would still be nice if my changes could be added to AOSP to align linux with the other targets. |
You could contribute them to AOSP directly. Then they will trickle down to here. |
It appears the files changed in buildSrc in this PR do not exist in AOSP version. The changes are all in compose-multiplatform-core specific files, so I cannot add it in AOSP. It needs to be added in the Jetbrains fork. I do not see how this could cause any conflicts if changes in buildSrc are all Jetbrains specific code. @MatkovIvan could you reconsider merging this? Or should I just drop the whole idea of a linuxMain sourceset? It is needed by many compose modules to add linux support. |
Exactly. That's why merging this will require by-hand adoption to AOSP version later.
It's a good option even if it's not used in fork's
I still see it as helper convenience util, but not as a requirement for adding
My objections are not strong here. cc @igordmn for final word |
It is not that adding it in every build.gradle will not work, but I think a new function would be a better solution. If you look at the other platforms, you see functions like |
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.
I've re-checked the current status of AOSP and it's already there, so no blockers from me.
Sorry for previous confusion and thanks for the contribution
Please, fix CI. P.S. it is not a complete list of checks, we have an issue running them for external PRs on TeamCity at the moment |
@igordmn fixed by rebasing and adding linux() shortcut to the affected modules. https://github.com/Thomas-Vos/compose-multiplatform-core/actions/runs/15138676522 |
This PR creates a new
linuxMain
source set which depends onnativeMain
. It can be created withlinux()
, this is similar to how it is done for other targets.Replaced individual
linuxX64()
/linuxArm64()
targets with this newlinux()
call. I did not add linux support to any new modules, this PR is so the actual PR supporting Linux for Compose UI will be a bit smaller. The additional linuxMain source set is required for that.Testing
N/A
Release Notes
N/A