Use default target hierarchy to setup build targets #272
Conversation
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
* remove `IR` in JS target, as it's default now * additional minor changes to use nicer APIs for js testTasks and sourceSet dependencies * group native targets declaration by platform, to better understand which targets are enabled - maybe it's fine to even inline `nativeTargets` function, so that all targets will be in one place
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.
Fixes #147
Note: using
applyDefaultHierarchyTemplatewith extended hierarchy isexperimental+ accessors for WasmJs and WasmWasi will be available only in KGP 2.0.Feel free to integrate it now or wait when above points will be resolved.
Minor additional changes:
IRin JS target, as it's default nownativeTargetsfunction, so that all targets will be in one place