whether it can make runnable jar without other setting

Asked by larryli

Now, I have read the following page.
https://answers.launchpad.net/sikuli/+question/685465
https://answers.launchpad.net/sikuli/+faq/2947

for 2.0.2 whether it is possible to make one runable jar or file including the custom script, without install jython or sikuli or java
it can use on another PC directly?

as current understand, it can run from the command line,
java -jar sikulixapi-2.0.3.jar -r custome.jar #custome.jar is created from sikulixIDE, export as jar.

BTW, for SikulixIDE to export script as jar, it will display "not set", but jar is created already, what mean "not set"

thanks

Question information

Language:
English Edit question
Status:
Answered
For:
SikuliX Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
RaiMan (raimund-hocke) said :
#1

--- for 2.0.2 whether it is possible to make one runable jar or file including the custom script, without install jython or sikuli or java

principally this would be possible, but is not an intended feature for SikuliX.

you could create an installer exe with tools like nsis.

Or have a look at portable apps, which can be used to create containers, that can be run from a stick or cloud, without leaving anything on the running system.

Be aware:
- the size would be above 200 MB
- the startup-time would be some minutes

SikuliX will always need Java and sikulixapi.jar available at runtime.

... and Jython, if you decide to implement your SikuliX app in Python.

Currently using JavaScript as scripting language, would make Jython not needed (but it is announced, that the Java script engine will be removed from Java somewhen in the future).

Another options are to write your app in plain Java or in any other Java aware language, that does not need a runtime environment besides Java.

So in the end: SikuliX at least needs Java and sikulixapi.jar on the system, that your app should run on.

--- BTW, for SikulixIDE to export script as jar, it will display "not set",

this is a bug and fixed in 2.0.4 (should display the created jar's path)

Can you help with this problem?

Provide an answer of your own, or ask larryli for more information if necessary.

To post a message you must log in.