Env related issue - I think fanlaunch should not directly declare configuration options but rather import it from standard fan configuration source, etc/ by default.

-Xmx heap limitation should be bumped to 512 megabytes in meantime because it is needed to compile fantom source code itself on 64-bit machines (the compilation process takes about 300m).

It'd also be nice if etc/sys/config.props was marked as wind32 configuration file only - I wasted two hours trying to adjust heap there before I found out that I was doing a silly and futile attempt.

I think it would be great if the bash script parsed config.props to get the Java options. But it is beyond my Bash skill level, and honestly I'd rather claw my eyes out than try to figure out how do it in Bash (if anyone else wants a go at it, might be a nice feature). Although it is probably just as easy to tweak fanlaunch when you want to change JVM options.

It shouldn't be that hard I think I could do it. What should other options besides java.options do in fanlaunch?

essentially the same stuff that the win32 C code does, although java.options is probably the only thing that really matters

OK, I'll have a look at it.

katox submitted a patch to read the java options from etc/sys/config.props

changeset

So you can tweak memory settings there now