On Win, Commit 1d37de8 ant -Drelease=true noplay fails, while ant -noplay succeeds

Open Source Development
1

JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8 -Xmx8g -XX:MaxMetaspaceSize=256m -XX:MaxDirectMemorySize=256m -Xss128k
fails

ant -Drelease=true -Dlocale=en noplay succeeds

Can we use en and zh_CN?

ant -Drelease=true -Dlocale=en,zh_CN noplay ？

2

This works for me on macOS. Can you provide the specific error message(s) you encounter when compiling on Windows?

3

Regarding the failure with JAVA_TOOL_OPTIONS: -Xss128k is extremely low for a GWT build, which involves deep recursion. The default is typically 1024k. Restricting it to 128k likely causes a StackOverflowError in the JVM or the compiler itself.

As for ant -Drelease=true -Dlocale=en,zh_CN noplay: Yes, GWT supports comma-separated locales. However, this instructs the compiler to build permutations for both languages in a single run, effectively doubling the memory and time required. If your machine is already resource-constrained (implied by your strict memory settings), this might trigger an OOM. If the build fails, try increasing -Xmx or building them sequentially.

4

I will point out that we set the -Xss flag to 4M and the -Xmx flag to 6G in appengine/build.xml. Your mileage may vary if you use smaller values but expect a greater chance of a build failure.