SQLiter - 1.8 Beta Testing

[KatieGalvin]

Perform the list of sanity checks on your work projects (it mostly consists of basic actions).

• Compile your project with a current Kotlin version.
• Check the highlighting in different IDE modules.
• Compile the project with the EAP Kotlin version and install the EAP IDE plugin.
• Verify that the project re-imported successfully.
• Check that highlighting from p.2 works not worse than before.
• Compile the project again and look for new surprising warnings.
• Change something in the code and check if incremental compilation works.
• Run your tests with a new Kotlin version.
• Stop at some well-known piece of code, run the debugger and try stepping.
• Look for performance issues in compilation, runtime, re-import or IDE behavior.

Pay additional attention to these features and subsystems if applicable to your use case:

• Kotlin Gradle plugin: lots of changes in all typical usage scenarios
• The new Gradle Incremental compilation, which we plan to stabilize soon
• Expose compiler flags via Gradle lazy properties
• Ability to not fallback with compiler daemon by default
• arm64 support for watchOS targets
• Xcode 14 and new Objective-C frameworks support in Kotlin/Native

[samhill303]

Test RC version, not beta now that it's out

[hfhbd]

1.8.0 is out and I get some problems updating sqldelight to 1.8.0 with the native driver (https://github.com/cashapp/sqldelight/pull/3752):

> Task :drivers:native-driver:linkDebugTestIosX64
e: /Applications/Xcode_14.0.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld invocation reported errors
The /Applications/Xcode_14.0.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld command returned non-zero exit code: 1.

> Task :drivers:native-driver:linkDebugTestIosX64 FAILED
output:
Undefined symbols for architecture x86_64:
  "_sqlite3_bind_blob", referenced from:
      _co_touchlab_sqliter_sqlite3_sqlite3_bind_blob_wrapper69 in result.o

Would downgrading Xcode help as a workaround?

[kpgalligan]

Kotlin 1.8 changes how linker flags are applied. The Sqldelight plugin used to silently add -lsqlite3, but now that probably doesn't carry over. You'll need to add that to your Kotlin config directly or Xcode "Other Linker Flags".

For now, to apply this in Kotlin, use the following:

cocoapods {
        framework {
            linkerOpts("-lsqlite3") //<-- Add this
        }
}

If not using CocoaPods, something like the following:

kotlin {
    ios {
        binaries.framework {
            linkerOpts("-lsqlite3") //<-- Add this
        }
    }
}

This is also a change for SqlDelight, but frankly, I think we were all surprised 1.8 got released on New Years week :)

[hfhbd]

@kpgalligan I think, I got a workaround based on #90, at least for sqldelight (https://github.com/cashapp/sqldelight/pull/3752/commits/1810a86a3bfddac96d76b8f51e98315b376ac573). I am waiting for the CI, but locally it works. And yeah, Jetbrains can say Kotlin 1.8 was released in 2022 :D

[kpgalligan]

I think you could simplify that a bit:

binaries.configureEach {
      linkerOpts += ["-lsqlite3"]
    }

But I'd have to break out the sqldelight to try it out, and I'm not doing a lot of Groovy config these days to know if that syntax would work without trying it.

[hfhbd]

You are right, this syntax works and is nicer, thanks.