Feature: Allowing alias names for kotlin targets#20
Merged
kdroidFilter merged 2 commits intoMay 13, 2026
Conversation
- Replace hardcoded "jvmMain" and "jvmTest" with dynamic target discovery based on the kotlin target thus allowing naming alias - Included mandatory check for JVM target, throwing GradleException if missing - Refactor mapTargetToPlatform with cleaner logic for architecture detection - Add little logging for native target and alias identification
Moved Hardcoded version number and libraries to libs.versions.toml and read via Libraries.kt
Contributor
Author
|
try this version and let me know if any changes required |
Collaborator
|
Thank you very much :) Great job ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 Description
This PR addresses allowing alias names for kotlin targets, primarily focusing on the
KotlinNativeExportPluginbased on the issue #19📄 Motivation and Context
Hardcoded
kotlintarget names were generating no code forJFFAPI when projects used custom aliases or non-standard naming conventions for theirkotlintargets. By allowing alias names, the plugin is now more robust and flexible.🧪 How Has This Been Tested?
./gradlewbuild on projects using standard naming conventions.📦 Types of changes
✅ Checklist