GeezerVison is showing github.com — Build updates for v5 by catilac · Pull Request #1587 · processing/processing4
Conversation
We no longer need enableWebGPU. Updated code to reflect that. Review each commit.
You can now just run ./gradlew run or from IntelliJ you should be able to just build (after specifying correct build settings)
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We probably should have a mechanism to download pre-built libprocessing binaries at some point but that can be a follow up. Thanks for doing htis!
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
catilac reacted with thumbs up emoji
catilac reacted with heart emoji
All reactions
-
👍
1 reaction
-
❤️
1 reaction
|
|
|
|
|
onlyIf { !jextractDirectory.exists() }
|
|
|
}
|
|
|
val jextractVersionString = "22-jextract+6-47"
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a big deal for this but there might be a jextract for java 25 available at this point.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see there is an early build with the string "25-jextract+2-4"
(listed here: https://jdk.java.net/jextract/)
should be fine to use an early build at this point. but I can put it in a follow on !
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
How does one test this PR? Anything specific I should be trying?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
@tychedelia yes! will follow up
build broken bc of linux i will try to fix before merging
@SableRaf can you run locally? and use BUILD.md to to update your intellij config?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
|
Hi @catilac,
I followed the instructions in BUILD.md but, after switching to JVM 25, I get the following build error:
16:36:42: Executing 'updateDaemonJvm --jvm-version "25" --jvm-vendor "adoptium"'…
Starting Gradle Daemon...
Gradle Daemon started in 1 s 961 ms
Kotlin does not yet support 25 JDK target, falling back to Kotlin JVM_24 JVM target
> Task :buildSrc:checkKotlinGradlePluginConfigurationErrors SKIPPED
> Task :buildSrc:pluginDescriptors UP-TO-DATE
> Task :buildSrc:processResources NO-SOURCE
> Task :buildSrc:compileKotlin
Kotlin does not yet support 25 JDK target, falling back to Kotlin JVM_24 JVM target
w: Inconsistent JVM Target Compatibility Between Java and Kotlin Tasks
Inconsistent JVM-target compatibility detected for tasks 'compileJava' (25) and 'compileKotlin' (24).
This will become an error in Gradle 8.0.
Solution: Consider using JVM Toolchain: https://kotl.in/gradle/jvm/toolchain
Learn more about JVM-target validation: https://kotl.in/gradle/jvm/target-validation
> Task :buildSrc:compileJava NO-SOURCE
> Task :buildSrc:compileGroovy NO-SOURCE
> Task :buildSrc:classes UP-TO-DATE
> Task :buildSrc:jar UP-TO-DATE
> Task :plugins:library:checkKotlinGradlePluginConfigurationErrors SKIPPED
> Task :plugins:library:compileKotlin UP-TO-DATE
> Task :plugins:library:compileJava NO-SOURCE
> Task :plugins:library:pluginDescriptors UP-TO-DATE
> Task :plugins:library:processResources UP-TO-DATE
> Task :plugins:library:classes UP-TO-DATE
> Task :plugins:library:jar UP-TO-DATE
> Task :updateDaemonJvm
[Incubating] Problems report is available at: file:///Users/raphael/Documents/GitHub/processing4/.build/reports/problems/problems-report.html
Deprecated Gradle features were used in this build, making it incompatible with Gradle 10.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/9.1.0/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
7 actionable tasks: 1 executed, 6 up-to-date
FAILURE: Build failed with an exception.
* What went wrong:
Class org.gradle.jvm.toolchain.JvmVendorSpec does not have member field 'org.gradle.jvm.toolchain.JvmVendorSpec IBM_SEMERU'
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to generate a Build Scan (Powered by Develocity).
> Get more help at https://help.gradle.org.
BUILD FAILED in 25s
16:37:07: Execution finished 'updateDaemonJvm --jvm-version "25" --jvm-vendor "adoptium"'.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
SableRaf
commented
Oct 25, 2026
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
|
Bumping the foojay resolver plugin to 1.0.0 seems to fix it (as suggested by Claude)
plugins {
id("org.gradle.toolchains.foojay-resolver-convention") version "1.0.0"
}
Claude wrote:
This is a version incompatibility between Gradle and the Foojay resolver plugin. JvmVendorSpec.IBM_SEMERU was deprecated in Gradle 8 and removed in Gradle 9. Older versions of the Foojay resolver still reference it, and the failure shows up as soon as you pass a vendor, here adoptium. Your main branch most likely declares something like 0.8.0 or 0.9.0 in settings.gradle.kts.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
@SableRaf thanks so much for checking this. foojay is already pinned to 1.0.0 in main. could you try this again? I'm wondering why it's not in this branch though...
➜ processing4 git:(main) rg foojay
gradle/plugins/settings.gradle.kts
2: id("org.gradle.toolchains.foojay-resolver-convention") version "1.0.0"
|
SableRaf reacted with thumbs up emoji
SableRaf reacted with eyes emoji
All reactions
-
👍
1 reaction
-
👀
1 reaction
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
foojay is already pinned to 1.0.0 in main. could you try this again?
It works on main!
|
catilac reacted with hooray emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Reviewers
SableRaf
Awaiting requested review from SableRaf
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|