WASM_GC - generation of runtime JS

[kenchis]

Currently I copy the required runtime javascript of the new WASM garbage collector proposal from the github project manually in my project.
Since the old WASM backend generates it during the build phase using maven/gradle it makes totally sense to generate it for the new WASM GC backend, too. I assume the script strongly corresponds to the release version?

[konsoletyper]

TeaVM copies it. What build system are you using?

[kenchis]

I am using maven, since version 0.12.0, currently 0.12.1
Did you add the generation recently? I know for sure it was not there in 0.12.0

Edit: I did a quick check. It seems it is not created during my maven build:

<execution> <id>wasm_gc</id> <goals> <goal>compile</goal> </goals> <configuration> <stopOnErrors>true</stopOnErrors> <mainClass>client.teavm.JSIDPlay2TeaVM</mainClass> <targetDirectory> ${project.build.directory}/classes/server/restful/webapp/teavm/wasm_gc</targetDirectory> <targetFileName>${project.artifactId}.wasm</targetFileName> <debugInformationGenerated>false</debugInformationGenerated> <sourceMapsGenerated>false</sourceMapsGenerated> <sourceFilesCopied>false</sourceFilesCopied> <wasmExceptionsUsed>true</wasmExceptionsUsed> <targetType>WEBASSEMBLY_GC</targetType> <optimizationLevel>FULL</optimizationLevel> <minHeapSize>256</minHeapSize> <maxHeapSize>1024</maxHeapSize> </configuration> </execution>

[konsoletyper]

For Maven you need to specify this task explicitly:

          <execution>
            <id>web-client-runtime</id>
            <goals>
              <goal>copy-webassembly-gc-runtime</goal>
            </goals>
            <configuration>
              <targetDirectory>\${project.build.directory}/runtime-output-dir</targetDirectory>
            </configuration>
          </execution>

The reason for this was that this runtime is basically static file. The idea was that in some cases you can generate multiple WebAssembly modules and re-use this runtime between them.

[kenchis]

Yes, that works.
But for simplicity it could be better to just use a tag in the main execution step, instead of needing two of them:
<includeRuntimeJs>true</includeRuntimeJs>