Add Linux X64 Support

[napperley]

This PR partly addresses issue #45 by only adding support for a single Kotlin Native target (linuxX64), and is the successor to PR #103 . Implementation of this PR is based on the existing JS implementation with some minor adaptations made to make it work with the Kotlin Native linuxX64 target. Use of dependencies is minimal with only the Kotlin Native Standard library, and POSIX being used. Most Linux distributions have built-in support for POSIX (Android is one of the main exceptions).

The latest stable version of Kotlin is used due to Kotlin Native currently not having proper backwards compatibility. It remains unknown if this situation will be resolved with the Kotlin 1.4 release that is arriving soon.

[oshai]

@napperley is the PR ready to be merged from your perspective? If so I will create an artifact from this to verify it's ok and after we test that I will merge.

[napperley]

The PR is ready to be merged.

[oshai]

@napperley I tried to deploy 1.8.0.1.
bintray publish seems fine but I couldn't publish to github packages with the following error:

Caused by: org.gradle.internal.resource.transport.http.HttpErrorStatusCodeException: Could not PUT 'https://maven.pkg.github.com/MicroUtils/kotlin-logging/io/github/microutils/kotlin-logging-js/1.8.0.1/kotlin-logging-js-1.8.0.1.jar'. Received status code 422 from server: Unprocessable Entity

Did you encounter something similar?

[napperley]

I have encountered the 422 error before but haven't found a way to resolve it. One theory for the error is that the same artifact (GitHub package) exists on GitHub Packages therefore the publishing fails. Unfortunately GitHub doesn't provide a way to remove a individual artifact (GitHub package) from GitHub Packages.

[oshai]

I managed to release only the native artifact to github in version 1.8.0.3. Can you check that it looks ok?
If so, we might be able to exclude the js and jvm from the github publish and continue like that. Right now I just did it by commenting out those modules.

[napperley]

Did a quick visual inspection of the GitHub package. Everything looks ok 👍 .

[napperley]

All is not well. Tried to use the GitHub linuxx64 Package in a test project, and Gradle cannot find it. Using the following in the build file:

// ...
repositories {
    jcenter()
    mavenCentral()
    maven {
        url = uri("https://maven.pkg.github.com/MicroUtils/kotlin-logging")
    }
}

kotlin {
    linuxX64 {
        compilations.getByName("main") {
            dependencies {
                val kotlinLoggingVer = "1.8.0.3"
                implementation("kotlin-logging:kotlin-logging:$kotlinLoggingVer")
            }
        }
        // ...
    }
}
// ...

Note that the base URL works: https://maven.pkg.github.com

[oshai]

I think that there is a line that should be changed:

implementation("kotlin-logging:kotlin-logging-linuxx64:$kotlinLoggingVer")

Note the artifact id: kotlin-logging-linuxx64

[napperley]

That doesn't make a difference. Usually with Kotlin Native libraries the name of the module is omitted when adding a Kotlin Native library as a dependency, eg:
implementation("kotlin-logging:kotlin-logging:1.8.0.3")

[oshai]

Might be, but as far as I understand that is how gradle find the artifact. See here: https://github.com/MicroUtils/kotlin-logging/packages/286126

[oshai]

Can you try also to see if there is a difference from the version you managed to publish?

[napperley]

Turns out one has to authenticate (via a username and token) in order to access the GitHub Packages Maven repository which isn't going to work (the Maven repositories are private) 😦 . GitLab Maven repositories by comparison can be accessed by anyone (are public) for downloading artifacts via Gradle or Maven.

[oshai]

Turns out one has to authenticate in order to access the GitHub Packages Maven repository which isn't going to work 😦 .

This is strange, because via the ui you can download it without even being signed-in.

[oshai]

@napperley it seems we are a bit stuck here. What do you think about merging the code changes without the changes in the build? so we actually won't publish those artifacts yet but we'll have the code ready until we solve it, maybe with changes to multiplatform framework in kotlin.

[napperley]

@oshai - If you are referring to removing the configuration for GitHub Packages then I can have it removed from the build file. Hopefully artifacts hosted by GitHub Packages in the future will be publicly accessible through Gradle.

[oshai]

Thanks @napperley , I merged it. Hope the packaging issue will be solved soon.