© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
based on the related question.
from comment #1:
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>
... 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.