Question #260735 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/260735
Status: Open => Answered
RaiMan proposed the following answer:
LOL, I am just struggling myself, to create an exe with Launch4J for the
IDE package in version 1.1.0
the current implementations of SikuliX will not work, if you pack everything
into the exe,
only the version launch-only work out of the box
<launch4jConfig>
<dontWrapJar>true</dontWrapJar>
... but I guess, this is not what you want ;-)
If you wait a few days: there will be sikulixapi.jar, that can be
wrapped in the exe.
The problem with Launch4J:
If anything goes wrong inside, as in this case, the exe simply dies without any
comment.
The problem with SikuliX:
SikuliX exports the native libraries at runtime to the libs folder.
this currently is based on the existence of a real jar, which is not available
in this case of wrapped exe.
The solution:
I have already added a feature, to just access the resources from class path.
This is not yet available in sikulixapi.jar, but will be in a few days.
The libs will then be exported to temp.
In any case (as now): existing libs are checked and an export is only done, if
needed based on timestamp and the libs folder is added to system path at
runtime dynamically.
I will comment here, when ready
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.
_______________________________________________
Mailing list: https://launchpad.net/~sikuli-driver
Post to : [email protected]
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
