Tighten KTX version dependency
See original GitHub issueThe CLI tool should verify that the installed KTX-Software is not outdated by checking the output of toktx --version
.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Android KTX | Android Developers
To start using Android KTX, add the following dependency to your project's build.gradle file: ... Remember to append the version number to the...
Read more >Android Library seems to loose some informations upon ...
Android Library seems to loose some informations upon compilation ... is the method present and i have no dependency version conflict. if i ......
Read more >Android dependency 'androidx.core:core' has different version ...
Android dependency 'androidx.core:core' has different version for the compile (1.0.0) and runtime (1.0.1) classpath. You should manually set the same version ...
Read more >Add a map to your Android app (Kotlin) - Google Developers
Add Google Maps dependency ... <?xml version="1.0" encoding="utf-8"?> ... Include KTX dependencies in your app-level build.gradle file.
Read more >Android KTX - Viblo
Bạn phải thêm dependencies tương ứng với các version vào file build.gradle trong app. Android KTX chứa một single core module, nó cung...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
v4.0.0-rc1~6
refers to the exact commit that affectedtools/toktx
git path withv4.0.0-rc1
being the version tag and~6
subtracting six commits back from it. We should just ignore the last part here.I see, thanks – I suppose there’s no guarantee that a local build (possibly with edits) will be compatible with glTF-Transform in any case. So I’ll stick to the current checks, and just warn rather than throwing an error if the version isn’t within the expected range.