[request] Launch4J support: sikulixapi.jar should work, when wrapped into an exe
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
In Progress
|
Medium
|
RaiMan |
Bug Description
based on the related question: https:/
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.
Changed in sikuli: | |
status: | New → Fix Committed |
importance: | Undecided → High |
assignee: | nobody → RaiMan (raimund-hocke) |
milestone: | none → 1.1.0 |
Changed in sikuli: | |
milestone: | 1.1.0 → 2.0.0 |
description: | updated |
Changed in sikuli: | |
status: | Fix Committed → In Progress |
importance: | High → Medium |
Changed in sikuli: | |
milestone: | 2.0.0 → 2.1.0 |
Hi Raimund,
Is a nightly build via maven available that contains the fix? May you post the coordinates here?
Best regards,
Angelo