bsimmons
09/21/2020, 1:57 PMiosMain
. So far I've managed by just guessing names and such, but I'm wondering how do I actually get this working on a Mac? Any ideas?Samuel Michael
09/21/2020, 3:02 PMwhy
09/21/2020, 5:19 PMAlberto
09/21/2020, 6:06 PMSamuel Michael
09/21/2020, 10:02 PMLogan Knight
09/22/2020, 9:43 AMrun
and installDist -t
, but the js is not served. I have found that if I manually copy the js files to ${buildDir}/processedResources/jvm/main
they are served. First I don't know that this is the 'correct' place for them when using installDist
. Second for the life of me I can't seem to figure out how to get gradle to do a simple copy of the files to that dir. Are the js files supposed to be in that dir, and if so what would be a good or the proper way to make that happen?akapanina
09/22/2020, 10:38 AMJake
09/22/2020, 12:41 PMpackForXCode
function to pack a “fat binary” is that still the appropriate action?Daniele B
09/22/2020, 1:34 PMKotlin/React
, and I realized it’s really simple to make components, using Kotlin-DSL
HTML elements. I have started to create Web component functions that have exactly the same API of JetpackCompose composables (e.g. NavigationBar, NavigationItem).
So, I can now build a webApp with Jetpack composables, still using Kotlin! It’s really awesome.
I believe someone (maybe JetBrains itself) will eventually extend JetpackCompose to web, because it makes a lot of sense.
I can see in the near future we will just have 2 UI frameworks: JetpackCompose
(for Android, Desktop and Web) and SwiftUI
(for iPhone, iPad, Mac, etc.).
I don’t even think React will last, because JetBrains already gained so much expertise that they can easily write their own efficient web reactive framework in Kotlin/JS, based on StateFlow
using JetpackCompose components for the UI, bypassing React completely.
So, my suggestion for everyone is to really start learning JetpackCompose and SwiftUI, because this is going to be the base for any app of the future. All the rest will become legacy.Diego
09/22/2020, 2:51 PMjanvladimirmostert
09/23/2020, 7:19 AMjavaClass.getResourceAsStream("blah.txt")
doesn't seem to work when using that directory structure, works fine when it's a normal src/main/resources
structured projectKamilH
09/23/2020, 10:25 AMcoolcat
09/23/2020, 11:45 AM"$REPO_ROOT/../../../../../../private/var/folders/ps/l3tx8c517t19l8p14jq3zvsh0000gp/T/wrap12070loc/gradlew" -p "$REPO_ROOT" ::syncFramework \
Most other generated podspecs I have seen in sample projects look like
"$REPO_ROOT/../gradlew" -p "$REPO_ROOT" :core:syncFramework \
I am concerned it refers to a temporary folder on my machine which may disappear in future. Does anybody know what the problem may be?Hailong
09/23/2020, 1:23 PMTask :app:transformClassesWithStackFramesFixerForDebugException in thread "main" java.lang.IllegalArgumentException: Type without superclass: module-info at com.google.common.base.Preconditions.checkArgument(Preconditions.java:191) at com.google.devtools.build.android.desugar.DefaultMethodClassFixer.visit(DefaultMethodClassFixer.java:80) at org.objectweb.asm.ClassVisitor.visit(ClassVisitor.java:113) at com.google.devtools.build.android.desugar.InterfaceDesugaring.visit(InterfaceDesugaring.java:97) at org.objectweb.asm.ClassReader.accept(ClassReader.java:621) at org.objectweb.asm.ClassReader.accept(ClassReader.java:500) at com.google.devtools.build.android.desugar.Desugar.desugarClassesInInput(Desugar.java:477) at com.google.devtools.build.android.desugar.Desugar.desugarOneInput(Desugar.java:361) at com.google.devtools.build.android.desugar.Desugar.desugar(Desugar.java:314) at com.google.devtools.build.android.desugar.Desugar.main(Desugar.java:711)
Task :app:transformClassesWithDesugarForDebug FAILEDFAILURE: Build failed with an exception.
thalescm
09/23/2020, 3:29 PMapp
), not multiplatform, is not recognizing the code from the multiplatform module (named shared
).
Gradle sync is fine, so I imagine the problem is not on there.
app/build.gradle.kts:
plugins {
kotlin("jvm")
application
id("org.openjfx.javafxplugin") version("0.0.8")
kotlin("plugin.serialization")
}
dependencies {
<other jvm deps>
implementation(project(":shared"))
}
group = "group"
version = "1.0-SNAPSHOT"
application {
mainClass.set("pac.kage.MainKt")
}
javafx {
version = "12"
modules = listOf("javafx.controls", "javafx.fxml", "javafx.graphics")
}
tasks.withType<JavaExec>().configureEach {
doFirst {
println("Desktop classpath: ${classpath.asPath}")
jvmArgs = listOf(
"--module-path", classpath.asPath,
"--add-modules", "javafx.controls",
"--add-modules", "javafx.fxml",
"--add-modules", "javafx.graphics"
)
}
}
tasks.withType<Test>().configureEach {
useJUnitPlatform()
}
And the shared/build.gradle.kts:
plugins {
kotlin("multiplatform")
id("kotlinx-serialization")
}
kotlin {
jvm {
val main by compilations.getting {
output
}
}
sourceSets {
val commonMain by getting {
dependencies {
implementation(kotlin("stdlib-common"))
}
}
val jvmMain by getting {
dependencies {
implementation(ExternalDeps.jipes)
implementation(kotlin("stdlib"))
}
}
}
}
Kris Wong
09/23/2020, 5:55 PMJohn Gainfort
09/23/2020, 6:29 PMUnable to resolve dependency for ':app@debug/compileClasspath': Could not resolve tech.ctawave.cmcd:cmcd-android:0.0.1.
Has anyone run into this? gradle 6.6.1, kt 1.4.10, and I have set
android {
publishAllLibraryVariants()
}
within the library gradle. Any help is appreciated.ankushg
09/24/2020, 1:52 AMjw
09/24/2020, 5:27 PMStefMa
09/25/2020, 9:23 AMandroidTests
are compiled and running as well. Which is bad because I don't want this 🙃 .
can I somehow exclude the androidTest
sourceSet from the androidAndroidTest
sourceSet?
I tried already multiple things e.g. setting the srcDris
of android.sourceSet.androidTest.setSrcDirs()
but it seems they will always execute them. Regardless of what I put into the srcDirs
.Evan
09/25/2020, 9:17 PMDispatchers.Main
.
Anyone else running into an error like this?Shawn Witte
09/26/2020, 4:47 AMexpect/actual
vs using an interface. I'm especially curious if there are use cases for expect/actual
that can't be solved with an interface or are obviously better suited to the expect/actual
pattern. I asked a question on the forums, but it didn't get any traction.Sam Garfinkel
09/26/2020, 10:42 PMJohn O'Reilly
09/27/2020, 10:59 AMwilliam
09/27/2020, 3:58 PMspierce7
09/28/2020, 12:11 AMHailong
09/28/2020, 3:07 AMnrobi
09/28/2020, 7:29 AMSqlDelight 1.4.3
native
dependency?
Can’t seem to resolve NativeSqliteDriver
, while AndroidSqliteDriver
worsk well. Kotlin 1.4.0
bodo
09/28/2020, 8:38 AMKamilH
09/28/2020, 12:27 PMcocoapods
plugin to my very simple library project and it fails at:
Execution failed for task ':podspec'.
> The Gradle wrapper is required to run the build from Xcode.
Please run the same command with `-Pkotlin.native.cocoapods.generate.wrapper=true` or run the `:wrapper` task to generate the wrapper manually.
As suggested I tried to run gradle wrapper
and it fails:
An exception occurred applying plugin request [id: 'org.jetbrains.kotlin.multiplatform', version: '1.4.10']
> Failed to apply plugin [id 'org.jetbrains.kotlin.multiplatform']
> The current Gradle version 5.4.1 is not compatible with the Kotlin Multiplatform plugin. Please use Gradle 6.0 or newer, or the previous version of the Kotlin plugin.
Why is that happening? In my gradle-wrapper.properties
I’m using distributionUrl=https\:<//services.gradle.org/distributions/gradle-6.6.1-bin.zip>
KamilH
09/28/2020, 12:27 PMcocoapods
plugin to my very simple library project and it fails at:
Execution failed for task ':podspec'.
> The Gradle wrapper is required to run the build from Xcode.
Please run the same command with `-Pkotlin.native.cocoapods.generate.wrapper=true` or run the `:wrapper` task to generate the wrapper manually.
As suggested I tried to run gradle wrapper
and it fails:
An exception occurred applying plugin request [id: 'org.jetbrains.kotlin.multiplatform', version: '1.4.10']
> Failed to apply plugin [id 'org.jetbrains.kotlin.multiplatform']
> The current Gradle version 5.4.1 is not compatible with the Kotlin Multiplatform plugin. Please use Gradle 6.0 or newer, or the previous version of the Kotlin plugin.
Why is that happening? In my gradle-wrapper.properties
I’m using distributionUrl=https\:<//services.gradle.org/distributions/gradle-6.6.1-bin.zip>
william
09/28/2020, 12:56 PM./gradlew --gradle-version 6.6.1
or whatever the upgrade command isKamilH
09/28/2020, 12:59 PMfind in path
5.4.1 there is no resultsgradle --version
and it indeed shows 5.4.1
gradle
gradle wrapper --gradle-version 6.6.1
FAILURE: Build failed with an exception.
* Where:
Build file 'PROJECT_PATH' line: 2
* What went wrong:
An exception occurred applying plugin request [id: 'org.jetbrains.kotlin.multiplatform', version: '1.4.10']
> Failed to apply plugin [id 'org.jetbrains.kotlin.multiplatform']
> The current Gradle version 5.4.1 is not compatible with the Kotlin Multiplatform plugin. Please use Gradle 6.0 or newer, or the previous version of the Kotlin plugin.
gradle
via `brew`:
brew upgrade gradle
then running
gradle wrapper
to install wrapper in the project directory and finally synchronizing projectwilliam
09/28/2020, 10:14 PMKamilH
09/29/2020, 5:18 AMgradle
couldn’t install it in the project because it was on too low version. After manually upgrading system-wise gradle to 6.1.1 it installed gradle wraper in the project properly