Activity log for bug #1411165

Date Who What changed Old value New value Message
2015-01-15 09:33:07 RaiMan bug added bug
2015-01-15 09:33:16 RaiMan sikuli: status New Fix Committed
2015-01-15 09:33:20 RaiMan sikuli: importance Undecided High
2015-01-15 09:33:23 RaiMan sikuli: assignee RaiMan (raimund-hocke)
2015-01-15 09:33:26 RaiMan sikuli: milestone 1.1.0
2015-06-24 05:45:35 RaiMan sikuli: milestone 1.1.0 2.0.0
2016-02-28 08:19:39 RaiMan bug added subscriber angelo
2016-02-28 15:59:01 angelo description 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>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. based on the related question: https://answers.launchpad.net/sikuli/+question/260735 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>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.
2016-02-28 16:33:12 RaiMan sikuli: status Fix Committed In Progress
2016-02-28 16:33:16 RaiMan sikuli: importance High Medium
2019-11-18 17:49:31 RaiMan sikuli: milestone 2.0.0 2.1.0