I would really, really like that expansion of environment variables would work for the <cmdLine> as well as for the <opt>.
I can see from the heap.c that it is not implemented there at all although it seems like it would be an obvious feature. Unfortunately I am not in a position to do it myself right now.
Which brings me to another question, is Launch4J being maintained at all lately? I haven't see any activity for quite a while.
Regards,
Jody
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd like this feature too. I wanted to use Launch4j to create Groovy binaries, which means having a way to add a path to a relative lib directory (aka to use %EXEDIR%) via GroovyStarter's --classpath argument. Was there any design reason this was intentionally not done?
Last edit: Keegan Witt 2017-01-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would really, really like that expansion of environment variables would work for the <cmdLine> as well as for the <opt>.
I can see from the heap.c that it is not implemented there at all although it seems like it would be an obvious feature. Unfortunately I am not in a position to do it myself right now.
Which brings me to another question, is Launch4J being maintained at all lately? I haven't see any activity for quite a while.
Regards,
Jody
I'd like this feature too. I wanted to use Launch4j to create Groovy binaries, which means having a way to add a path to a relative lib directory (aka to use %EXEDIR%) via GroovyStarter's --classpath argument. Was there any design reason this was intentionally not done?
Last edit: Keegan Witt 2017-01-03