GraalVM native-image support doesn't work

[Moubassher]

Describe the bug
It says in the README section:
GraalVM native-image support Sqlite JDBC supports GraalVM native-image out of the box starting from version 3.40.1.0. There has been rudimentary support for some versions before that, but this was not actively tested by the CI.
But I didn't find this to be accurate.
To Reproduce
Simply run: gradle NativeBuild. It works without adding the dependency, but once added it fails:
my version is:
'org.xerial:sqlite-jdbc:3.50.3.0'

Expected behavior
an exe produced with "gradle NativeBuild".

Logs
unfortunately, Gluonfx's output is not very helpful, it's just NativeCompile task fails.

Environment (please complete the following information):

• OS: [e.g. Windows 10]
• CPU architecture: [e.g. x86_64]
• sqlite-jdbc version [e.g. 3.50.3.0]

Additional context
NA

[gotson]

could you provide some kind of logs or details on the error?

[Moubassher]

Yes, here is my build: I installed Windows 10 SDK, and start a x64 native tools command prompt for 2022 VS (as an admin), then cd into the root of the project. Then I simply go:
gradle nativeRunAgent, and it succeeds by creating config files under resources/META_INF...
when I then run: gradle nativeBuild, it fails at linking:
Here's my gradle build (I created this project specifically to debug this issue, so it's minimal):

plugins {
    id 'java'
    id 'application'

    id 'org.openjfx.javafxplugin' version '0.1.0'
   id 'com.gluonhq.gluonfx-gradle-plugin' version '1.0.27'  // GluonFX
}

group 'com.example'
version '1.0-SNAPSHOT'

repositories {
    mavenLocal()
    mavenCentral()
    maven { url 'https://jitpack.io' }
}

tasks.withType(JavaCompile) {
    options.encoding = 'UTF-8'
}

application {
    mainClass = 'com.example.demo.HelloApplication'

    applicationDefaultJvmArgs = [
            '--add-opens', 'java.base/java.lang=ALL-UNNAMED',
            '--add-opens', 'java.base/java.lang.reflect=ALL-UNNAMED',
            '--add-opens', 'java.base/java.util=ALL-UNNAMED'
    ]
}

def javafxVersion = '23.0.1'
javafx {
    version = javafxVersion
    modules = ['javafx.controls', 'javafx.fxml', 'javafx.web', 'javafx.media', 'javafx.graphics']
}




dependencies {

    implementation 'com.zaxxer:HikariCP:7.0.2'

  //  implementation 'com.contextSoftwareSolutions:ourToolbox:1.0.0'

  //  implementation 'org.xerial:sqlite-jdbc:3.50.3.0'

    testImplementation 'org.junit.jupiter:junit-jupiter-api:5.10.2'
    testRuntimeOnly 'org.junit.jupiter:junit-jupiter-engine:5.10.2'
    testRuntimeOnly 'org.junit.platform:junit-platform-launcher:1.10.2'
}


run {
    jvmArgs += [
            "--add-modules=javafx.controls,javafx.fxml,javafx.media,javafx.web,javafx.graphics,javafx.base",
            "--module-path", configurations.runtimeClasspath.asPath,
            "--add-reads", "org.xerial.sqlitejdbc=ALL-UNNAMED"
    ]
}


gluonfx {
    target = "host"

    compilerArgs = [
            "-H:StripDebugInfo=true"
    ]
    verbose = true
}

test {
    useJUnitPlatform()
}

The error message I get is something like: Linking native executable hellofx.exe
LINK : fatal error LNK1120: 5 unresolved externals
collect2.exe: error: ld returned 1 exit status
the rest seems to be Gradle's stacktrace showing internals.
Running the command with --info --stacktrace doesn't help.

I appreciate your help in advance.

[Moubassher]

I just realized this line causes an error also:

 compilerArgs = [
            "-H:StripDebugInfo=true"
    ]

commenting it out causes the error to disappear. Putting it back causes the error to happen again.
PS: I can't, for the life of me use "pure" native-image tool. What kind of jar should I use it with? a fat jar created with Gradle? or Intellij? or a thin jar? I couldn't tell and I get errors I see for the first time in my 5 years of programming.

[kkriske]

This seems like an issue to log with the folks of Gluon, tests are running against stock native image, and GluonFX deviates quite a bit from native-image, especially in the linking step where you are seeing issues.

[Moubassher]

@kkriske Aha I think so. I downgraded sqlite to the driver version which is stated to be compatible and it resolved the issue. Closing the issue...
Thanks for your help