SWUpdate ERROR : feature 'archive' required - yocto

I am attempting to use SWUpdate to update my device kernel and device tree. However I am getting the error ERROR : feature 'archive' required. I have been told to configure SWUpdate to include archive then build it. To do this I run bitbake -c menuconfig swupdate. This creates a .config file which I use as a defconfig.
I have my bitbake file swupdate_%.bbappend which places this into the build
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI += "file://defconfig"
DEPENDS += " libarchive zstd"
My question is how do I properly configure and compile the SWUpdate recipe to include the archive library?
If I run bitbake -c menuconfig swupdate and enable ZSTD, archive, and SystemD followed by bitbake swupdate I get errors that zstd, archive and systemd headers cannot be found. Edit 1: This is resolved by adding DEPENDS += " libarchive zstd systemd" to the bitbake file. This then breaks my overall build. So it seems my real issue is I cannot properly get the defconfig into my image.
I found many repos on GitHub and I copied their folder structure and used their bitbake files to inspire my own. However when I get to building I get the error mentioned above. Can anyone point me in the right direction? I am willing to share more if needed.
Edit 2: I removed the defconfig from here and my project. I found that SWUpdate supports the function bitbake -c diffconfig swupdate. After making my changes I get an output file /build-fb/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/swupdate/2021.11-r0/fragment.cfg with the contents
CONFIG_SYSTEMD=y
CONFIG_ZSTD=y
CONFIG_ARCHIVE=y
CONFIG_LOCALE=y
I added this to my defconfig and built my image. Same issue.
Edit 3: I want to show how I build my image.
source setup-environment build-fb/
bitbake -c cleanall mainapplication-dev
bitbake mainapplication-dev
I take the image generated and program my SD card. Then I run
bitbake -c cleanall smg-image-swu
bitbake smg-image-swu
This creates my .swu file which I place onto the device using FileZilla. I then run swupdate -v -i smg-image-swu-imx6ull14x14evk.swu and get the following output:
root#imx6ull14x14evk:~# swupdate -v -i smg-image-swu-imx6ull14x14evk.swu
Swupdate v2021.11.0
Licensed under GPLv2. See source distribution for detailed copyright notices.
[INFO ] : SWUPDATE running : [main] : Running on smg-mx6 Revision 1.0
[INFO ] : SWUPDATE running : [print_registered_handlers] : Registered handlers:
[INFO ] : SWUPDATE running : [print_registered_handlers] : dummy
[INFO ] : SWUPDATE running : [print_registered_handlers] : flash
[INFO ] : SWUPDATE running : [print_registered_handlers] : lua
[INFO ] : SWUPDATE running : [print_registered_handlers] : raw
[INFO ] : SWUPDATE running : [print_registered_handlers] : rawfile
[INFO ] : SWUPDATE running : [print_registered_handlers] : rawcopy
[INFO ] : SWUPDATE running : [print_registered_handlers] : shellscript
[INFO ] : SWUPDATE running : [print_registered_handlers] : preinstall
[INFO ] : SWUPDATE running : [print_registered_handlers] : postinstall
[TRACE] : SWUPDATE running : [listener_create] : creating socket at /tmp/swupdateprog
[TRACE] : SWUPDATE running : [network_initializer] : Main loop daemon
[TRACE] : SWUPDATE running : [listener_create] : creating socket at /tmp/sockinstctrl
[TRACE] : SWUPDATE running : [network_thread] : Incoming network request: processing...
[INFO ] : SWUPDATE started : Software Update started !
[TRACE] : SWUPDATE running : [network_initializer] : Software update started
[TRACE] : SWUPDATE running : [extract_file_to_tmp] : Found file
[TRACE] : SWUPDATE running : [extract_file_to_tmp] : filename sw-description
[TRACE] : SWUPDATE running : [extract_file_to_tmp] : size 384
[TRACE] : SWUPDATE running : [get_common_fields] : Version 0.1.0
[TRACE] : SWUPDATE running : [parse_hw_compatibility] : Accepted Hw Revision : 1.0
[TRACE] : SWUPDATE running : [_parse_files] : Found compressed File: evccapplication-dev-imx6ull14x14evk.tar.gz --> / (/dev/update)
[TRACE] : SWUPDATE running : [_parse_scripts] : Found Script: update.sh
[ERROR] : SWUPDATE failed [0] ERROR : feature 'archive' required for 'evccapplication-dev-imx6ull14x14evk.tar.gz' in sw-description is absent!
[ERROR] : SWUPDATE failed [0] ERROR : Compatible SW not found
[ERROR] : SWUPDATE failed [1] Image invalid or corrupted. Not installing ...
[TRACE] : SWUPDATE running : [network_initializer] : Main thread sleep again !
[INFO ] : No SWUPDATE running : Waiting for requests...
[INFO ] : SWUPDATE running : [endupdate] : Swupdate *failed* !

The solution to this is to edit the above bbappend file to
FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
SRC_URI += "file://defconfig"
DEPENDS += " libarchive zstd"

Related

So i‘m trying to deploy a function on openfaas based on arm architecture,but i failed.Can someone tell me how to solve it?

my kubernetes is based on arm,with kubernetes1.22.4
my faas-cli command:
faas-cli build -f ./add.yml
the response code :
[0] > Building add.
Clearing temporary build folder: ./build/add/
Preparing: ./add/ build/add/function
Building: myw/add:latest with python template. Please wait..
Sending build context to Docker daemon 8.192kB
Step 1/31 : FROM --platform=${TARGETPLATFORM:-linux/amd64} ghcr.io/openfaas/classic-watchdog:0.2.0 as watchdog
---> 6f97aa96da81
Step 2/31 : FROM --platform=${TARGETPLATFORM:-linux/amd64} python:2.7-alpine
---> 8579e446340f
Step 3/31 : ARG TARGETPLATFORM
---> Using cache
---> a75f5a062540
Step 4/31 : ARG BUILDPLATFORM
---> Using cache
---> c90a8309e851
Step 5/31 : ARG ADDITIONAL_PACKAGE
---> Using cache
---> 4ee3e6fab2a3
Step 6/31 : COPY --from=watchdog /fwatchdog /usr/bin/fwatchdog
---> Using cache
---> 33d972637c65
Step 7/31 : RUN chmod +x /usr/bin/fwatchdog
---> Running in 6204e8546454
standard_init_linux.go:219: exec user process caused: exec format error
The command '/bin/sh -c chmod +x /usr/bin/fwatchdog' returned a non-zero code: 1
[0] < Building add done in 0.54s.
[0] Worker done.
Total build time: 0.54s
Errors received during build:
- [add] received non-zero exit code from build, error: The command '/bin/sh -c chmod +x /usr/bin/fwatchdog' returned a non-zero code: 1
then can someone tell me the currect way to build a function with arm in openfaas,and why this happened,did i do someting wrong?

jpackage on Windows: The system cannot find file, error 103

I am trying to package a ScalaFx app I built using jpackage and having trouble on windows (mac & linux work just fine).
I am building a fat jar using sbt assembly and then using jpackage to create a .msi however I am getting this error:
$ jpackage --win-shortcut --name krystalbull --app-version 0.1 --type msi -i target/scala-2.13/ --main-class com.krystal.bull.gui.GUI --main-jar krystal-bull-assembly-0.1.jar --icon src/main/resources/icons/krystal_bull.ico --verbose
shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
env:
pkg-assembly: krystal-bull-assembly-0.1.jar
pkg-name: krystalbull
pkg-version: 0.1
JAVA_HOME_16.0.1_x64: C:\hostedtoolcache\windows\jdk\16.0.1\x64
JAVA_HOME: C:\hostedtoolcache\windows\jdk\16.0.1\x64
JAVA_HOME_16_0_1_X64: C:\hostedtoolcache\windows\jdk\16.0.1\x64
[21:10:32.469] Running candle.exe
[21:10:32.541] Running C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe
[21:10:34.005] Running light.exe
[21:10:34.024] Running C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe
[21:10:35.848] Detected [light.exe] version [3.11.2.4516].
[21:10:35.848] Detected [candle.exe] version [3.11.2.4516].
[21:10:35.849] WiX 3.11.2.4516 detected. Enabling advanced cleanup action.
[21:10:46.540] Command:
jlink --output C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\runtime --module-path C:\\hostedtoolcache\\windows\\jdk\\16.0.1\\x64\\jmods --add-modules jdk.management.jfr,java.rmi,jdk.jdi,jdk.charsets,jdk.xml.dom,java.xml,java.datatransfer,jdk.jstatd,jdk.httpserver,java.desktop,java.security.sasl,jdk.zipfs,java.base,jdk.crypto.ec,jdk.javadoc,jdk.management.agent,jdk.jshell,jdk.editpad,jdk.jsobject,java.sql.rowset,jdk.sctp,jdk.jlink,jdk.unsupported,java.smartcardio,java.security.jgss,java.compiler,jdk.nio.mapmode,jdk.dynalink,jdk.unsupported.desktop,jdk.accessibility,jdk.security.jgss,java.sql,jdk.incubator.vector,java.xml.crypto,java.logging,java.transaction.xa,jdk.jfr,jdk.crypto.cryptoki,jdk.net,java.naming,jdk.internal.ed,java.prefs,java.net.http,jdk.compiler,jdk.naming.rmi,jdk.internal.opt,jdk.jconsole,jdk.attach,jdk.crypto.mscapi,jdk.internal.le,java.management,jdk.jdwp.agent,jdk.internal.jvmstat,jdk.incubator.foreign,java.instrument,jdk.management,jdk.security.auth,java.scripting,jdk.jdeps,jdk.jartool,jdk.jpackage,java.management.rmi,jdk.naming.dns,jdk.localedata --strip-native-commands --strip-debug --no-man-pages --no-header-files
[21:10:46.540] Output:
WARNING: Using incubator modules: jdk.incubator.vector, jdk.incubator.foreign
[21:10:46.544] Returned: 0
(loaded from file D:\a\krystal-bull\krystal-bull\src\main\resources\icons\krystal_bull.ico).
[21:10:46.560] Using default package resource WinLauncher.template [Template for creating executable properties file] (add krystalbull.properties to the resource-dir to customize).
[21:10:47.532] MSI ProductCode: c47093f7-318f-3c33-b6f9-e8a8c4adb014.
[21:10:47.533] MSI UpgradeCode: c62bde9b-3ba1-3197-8853-ba4770495959.
[21:10:47.536] Using default package resource main.wxs [Main WiX project file] (add main.wxs to the resource-dir to customize).
[21:10:47.537] Using default package resource overrides.wxi [Overrides WiX project file] (add overrides.wxi to the resource-dir to customize).
[21:10:47.540] Preparing MSI config: D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi.
[21:10:47.541] Generating MSI: D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi.
[21:10:47.552] Running C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull
[21:10:50.004] Command:
C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe -nologo C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\main.wxs -ext WixUtilExtension -arch x64 -out C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\main.wixobj -dJpAppDescription=krystalbull -dJpAppVersion=0.1 -dJpProductCode=c47093f7-318f-3c33-b6f9-e8a8c4adb014 -dJpAppName=krystalbull -dJpAllowUpgrades=yes -dJpProductUpgradeCode=c62bde9b-3ba1-3197-8853-ba4770495959 -dJpIsSystemWide=yes -dJpAllowDowngrades=yes -dJpIcon=C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\krystalbull.exe -dJpAppVendor=Unknown -dJpConfigDir=C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config
[21:10:50.004] Output:
main.wxs
[21:10:50.005] Returned: 0
[21:10:50.005] Running C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull
[21:10:51.344] Command:
C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe -nologo C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf -ext WixUtilExtension -arch x64 -out C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\bundle.wixobj
[21:10:51.344] Output:
bundle.wxf
[21:10:51.346] Returned: 0
[21:10:51.348] Running C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull
[21:10:53.013] Command:
C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe -nologo -spdb -ext WixUtilExtension -out D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi -sice:ICE27 -loc C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\MsiInstallerStrings_en.wxl -cultures:en-us C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\main.wixobj C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\bundle.wixobj
[21:10:53.015] Output:
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(41) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\FileMenu$anon$2.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(56) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$10$anon$21$anonfun$lessinit$greater$1.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(71) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\SettingsMenu$anon$5.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(111) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$4.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(116) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$4.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(151) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$28.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(206) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\CreateNumericEventDialog$anon$6.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(221) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$10$anon$16.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(226) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\landing\LandingPane$anon$5.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(236) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$10.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(256) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$10$anon$22.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(271) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\CreateEnumEventDialog$anon$12$anon$13$anon$14.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(301) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\TaskRunner$anon$1$anon$2.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(336) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$10$anon$11.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(356) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$10$anon$16.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(366) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\CreateNumericEventDialog$anon$4.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(391) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\ViewMenu$anon$9.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(411) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\CreateEnumEventDialog$anon$1.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(426) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\HelpMenu$anon$13.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(436) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\landing\LandingPane$anon$7.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(451) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$21.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(461) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\ViewMenu$anon$9$anon$10.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(476) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$2.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(531) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$10$anon$14.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(546) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$2.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(556) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\CreateEnumEventDialog$anon$12$anon$15$anon$17.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(561) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$17.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(596) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\GUI$anon$1.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(601) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$23.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(631) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$18.class'.
.. more of the same ..
[21:10:53.019] Returned: 103
[21:10:53.020] java.io.IOException: Command [C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe, -nologo, -spdb, -ext, WixUtilExtension, -out, D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi, -sice:ICE27, -loc, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\MsiInstallerStrings_en.wxl, -cultures:en-us, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\main.wixobj, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\bundle.wixobj] in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull exited with 103 code
at jdk.jpackage/jdk.jpackage.internal.Executor.executeExpectSuccess(Executor.java:91)
at jdk.jpackage/jdk.jpackage.internal.WixPipeline.execute(WixPipeline.java:135)
at jdk.jpackage/jdk.jpackage.internal.WixPipeline.buildMsi(WixPipeline.java:99)
at jdk.jpackage/jdk.jpackage.internal.WinMsiBundler.buildMSI(WinMsiBundler.java:521)
at jdk.jpackage/jdk.jpackage.internal.WinMsiBundler.execute(WinMsiBundler.java:386)
at jdk.jpackage/jdk.jpackage.internal.Arguments.generateBundle(Arguments.java:664)
at jdk.jpackage/jdk.jpackage.internal.Arguments.processArguments(Arguments.java:538)
at jdk.jpackage/jdk.jpackage.main.Main.execute(Main.java:98)
at jdk.jpackage/jdk.jpackage.main.Main.main(Main.java:52)
[21:10:53.512] jdk.jpackage.internal.PackagerException: java.io.IOException: Command [C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe, -nologo, -spdb, -ext, WixUtilExtension, -out, D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi, -sice:ICE27, -loc, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\MsiInstallerStrings_en.wxl, -cultures:en-us, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\main.wixobj, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\bundle.wixobj] in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull exited with 103 code
at jdk.jpackage/jdk.jpackage.internal.WinMsiBundler.execute(WinMsiBundler.java:389)
at jdk.jpackage/jdk.jpackage.internal.Arguments.generateBundle(Arguments.java:664)
at jdk.jpackage/jdk.jpackage.internal.Arguments.processArguments(Arguments.java:538)
at jdk.jpackage/jdk.jpackage.main.Main.execute(Main.java:98)
at jdk.jpackage/jdk.jpackage.main.Main.main(Main.java:52)
Caused by: java.io.IOException: Command [C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe, -nologo, -spdb, -ext, WixUtilExtension, -out, D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi, -sice:ICE27, -loc, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\MsiInstallerStrings_en.wxl, -cultures:en-us, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\main.wixobj, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\bundle.wixobj] in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull exited with 103 code
at jdk.jpackage/jdk.jpackage.internal.Executor.executeExpectSuccess(Executor.java:91)
at jdk.jpackage/jdk.jpackage.internal.WixPipeline.execute(WixPipeline.java:135)
at jdk.jpackage/jdk.jpackage.internal.WixPipeline.buildMsi(WixPipeline.java:99)
at jdk.jpackage/jdk.jpackage.internal.WinMsiBundler.buildMSI(WinMsiBundler.java:521)
at jdk.jpackage/jdk.jpackage.internal.WinMsiBundler.execute(WinMsiBundler.java:386)
... 4 more
Error: Process completed with exit code 1.
Unfortunately this a bug in jpackage itself for windows
jpackage does not properly escape class file names for the WIX pre-processor.
See:
https://github.com/wixtoolset/issues/issues/6734
Bug tracker for the issue on openjdk:
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8282351
jpackage fails on Windows when application name differs from installer name as mentioned in the issue here
It works for me if I specify the same argument to --name is I specified for the app image.
(The same name as for the app-image command, but you might want to change the name).

How to solution the following error when build EmulatorPkg ?

when I run build -p EmulatorPkg\EmulatorPkg.dsc -t VS2019 -a X64, it show the following error
LINK : warning LNK4108:ָ /ALIGN ûָ /DRIVERӳܲ
LINK : warning LNK4001: δָļʹÿ
LINK : warning LNK4068: δָ /MACHINEĬΪ X86
LINK : error LNK2001: ޷ⲿ _ModuleEntryPoint
d:\edk2\edk2\Build\EmulatorX64\DEBUG_VS2019\X64\WinHost.lib : fatal error LNK1120: 1 ޷ⲿ
NMAKE : fatal error U1077: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\
MSVC\14.25.28610\bin\Hostx86\x64\link.exe": ش롰0x460
Stop.
Building ... d:\edk2\edk2\EmulatorPkg\BootModePei\BootModePei.inf [X64]
build.py...
: error 7000: Failed to execute command
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.25.28610\bin
\Hostx86\x86\nmake.exe /nologo tbuild [d:\edk2\edk2\Build\EmulatorX64\DEBUG_VS2019\X64\EmulatorPkg\Win
\Host\WinHost]
build.py...
: error F002: Failed to build module
d:\edk2\edk2\EmulatorPkg\Win\Host\WinHost.inf [X64, VS2019, DEBUG]
- Failed -
Build end time: 22:18:35, Apr.07 2020
Build total time: 00:00:13
but when build MdeModulePkg/MdeModulePkg.dsc, it not have any error.
The error was caused by missing support for VS2019 in this module.
Support was added upstream in commit 998d4c98b7c6 ("EmulatorPkg/WinHost: Add link flags for VS2019 tool chains.").

Allure plugin for VSTS returns error: Unknown Test Runner

The VSTS task: Generate Allure Report is failed.
The error is :
Unable to process command '##vso[results.publish type=Allure;mergeResults=true;publishRunAttachments=true;resultFiles=D:\a\1\s\allure-report\34;]' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)
Unknown Test Runner.
Question: can it be a bug or problem connected to configs?
Configurations:
.Net version: 4.6.1, Nunit3, Nunit3 allure adapter
Task to run tests is a Command Line task where I used nunit3-console.exe to run test.
Configurations for Allure plugin:
Results directory : allure-results
Target directory : allure-report/$(Build.BuildNumber)
The output logs:
****************************************************************************** Starting: Generate Allure Report
============================================================================== Task : Generate Allure Report Description : Generates Allure
report based on the test results Version : 1.0.0 Author :
Molecula Help : More
Information
============================================================================== C:\Program Files\nodejs\node.exe
D:\a_tasks\AllureGenerate_5c975f9d-1c3a-469f-b7c2-8907bf3eacfb\1.0.0\node_modules\allure-commandline\bin\allure
generate --output D:\a\1\s\allure-report\34 D:\a\1\s\allure-results
Command aborted due to exception {}.
org.apache.commons.exec.ExecuteException: Process exited with an
error: 1 (Exit value: 1) at
org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
at
org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
at
org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:153)
at
ru.yandex.qatools.allure.command.ReportGenerate.runUnsafe(ReportGenerate.java:48)
at
ru.yandex.qatools.allure.command.AbstractCommand.run(AbstractCommand.java:52)
at ru.yandex.qatools.allure.CommandLine.main(CommandLine.java:46)
org.apache.commons.exec.ExecuteException: Process exited with an
error: 1 (Exit value: 1) at
org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
at
org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
at
org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:153)
at
ru.yandex.qatools.allure.command.ReportGenerate.runUnsafe(ReportGenerate.java:48)
at
ru.yandex.qatools.allure.command.AbstractCommand.run(AbstractCommand.java:52)
at ru.yandex.qatools.allure.CommandLine.main(CommandLine.java:46) at
ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureReportGenerator.java:58)
at
ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureReportGenerator.java:53)
at ru.yandex.qatools.allure.AllureMain.main(AllureMain.java:48)
Exception in thread "main"
ru.yandex.qatools.allure.data.ReportGenerationException: Could not
find any allure results at
ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureReportGenerator.java:58)
at
ru.yandex.qatools.allure.data.AllureReportGenerator.generate(AllureReportGenerator.java:53)
at ru.yandex.qatools.allure.AllureMain.main(AllureMain.java:48)
Unable to process command '##vso[results.publish
type=Allure;mergeResults=true;publishRunAttachments=true;resultFiles=D:\a\1\s\allure-report\34;]'
successfully. Please reference documentation
(http://go.microsoft.com/fwlink/?LinkId=817296) Unknown Test Runner.
The default setting directory "allure-results" in the Allure task usually does not point to the actual path to result directory correctly since the path is different in different projects and environment. You need to update the setting to configure it to the actual path to the result directory manually.
According to the information you provided, the path to the result could be like this:
$(Build.SourcesDirectory)\SolutionFolder\ProjectFolder\bin\$(BuildConfiguration)\allure-results

Eclipse fails to build Java Card sample projects

I have installed the new release of Java Card Platform Development Kit, according to the following guide. This includes all the prerequisites, as well as version 3.0.5u2 of JCDK. As a heads up, I tried installing this on 2 different computers (one has Win7, the other Win10) and reinstalled everything on both.
The problem I'm encountering is that none of the sample projects will build properly. When I try to build the HelloWorld sample, for example, I get the following text printed in the build console:
[ INFO: ] Converter [v3.0.5]
[ INFO: ] Copyright (c) 1998, 2017, Oracle and/or its affiliates. All rights reserved.
[ INFO: ] conversion completed with 0 errors and 0 warnings.
[ INFO: ] Converter [v3.0.5]
[ INFO: ] Copyright (c) 1998, 2017, Oracle and/or its affiliates. All rights reserved.
[ INFO: ] conversion completed with 0 errors and 0 warnings.
Missing file containing component hashes.
usage: scriptgen [-options] -hashfile <hash file path> <cap File Path>
where options include:
-help Print this message and exit.
-o <filename> Output filename. default: stdout
-version Print version number and exit.
-nobanner Do not print banner.
-nobeginend Suppress "CAP_BEGIN", "CAP_END" APDU commands.
-package <pkgname> Package name.
While the regular console has this to say:
Executing "$JC_CLASSIC_HOME\bin/converter.bat" -debug -nobanner -out CAP JCA -classdir "$JC_CLASSIC_HOME\samples\classic_applets\HelloWorld\applet\bin" -d "$JC_CLASSIC_HOME\samples\classic_applets\HelloWorld\applet\deliverables" -exportpath "$JC_CLASSIC_HOME\api_export_files" -applet 0xA0:0x00:0x00:0x00:0x62:0x03:0x01:0x0C:0x01:0x01 com.sun.jcclassic.samples.helloworld.HelloWorld com.sun.jcclassic.samples.helloworld 0xA0:0x00:0x00:0x00:0x62:0x03:0x01:0x0C:0x01 1.0
Executing "$JC_CLASSIC_HOME\bin/scriptgen.bat" -package com.sun.jcclassic.samples.helloworld -o "$JC_CLASSIC_HOME\samples\classic_applets\HelloWorld\applet\apdu_scripts/cap-com.sun.jcclassic.samples.helloworld.script" "$JC_CLASSIC_HOME\samples\classic_applets\HelloWorld\applet\deliverables/com/sun/jcclassic/samples/helloworld/javacard/helloworld.cap"
java.io.FileNotFoundException: $JC_CLASSIC_HOME\samples\classic_applets\HelloWorld\applet\apdu_scripts\cap-com.sun.jcclassic.samples.helloworld.script (The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
... (stack trace)
Now, I'm not 100% sure, but I think that when I had version 3.0.5u1 installed, I was able to build the sample projects.
It seems the build process of the Java Card Classic Development Kit 3.0.5u2 (jcdk) Eclipse Plugin is broken. During the build of an java card applet, three scripts located in the bin subdirectory of the jcdk installation directory are executed (if using default applet settings in eclipse):
converter.bat generating the export file *.exp
converter.bat generating cap (and jca) file
scriptgen.bat generating the script files for installing the applet to a java card.
The problem is, that scriptgen requires a hashfile containing hashes for the applet components. You can see this if you decompile the class com.sun.javacard.scriptgen.Main of tools.jar in jcdk lib folder.
This hashfile is not generated during the eclipse build process, neither is the scriptgen script called with the corresponding program option "-hashfile <hash-file>". The only workaround currently is using the jcdk tools on the console manually. Therefor you can use the output of console in eclipse and adopt it for your needs.
Example output for a simple test applet:
Executing E:\eclipse-oxygen-64bit\JCDKit_305u2\bin/converter.bat -i -debug -out EXP -classdir G:\eclipse_javacard\workspace\TestJCDKApplet\bin -d G:\eclipse_javacard\workspace\TestJCDKApplet\deliverables -exportpath E:\eclipse-oxygen-64bit\JCDKit_305u2\\api_export_files -applet 0xD0:0x00:0x00:0x00:0x01:0x01:0x01 test.jcdk.applet.TestApplet test.jcdk.applet 0xD0:0x00:0x00:0x00:0x01:0x01 1.0
Executing E:\eclipse-oxygen-64bit\JCDKit_305u2\bin/converter.bat -i -debug -out CAP JCA -classdir G:\eclipse_javacard\workspace\TestJCDKApplet\bin -d G:\eclipse_javacard\workspace\TestJCDKApplet\deliverables -exportpath E:\eclipse-oxygen-64bit\JCDKit_305u2\\api_export_files -applet 0xD0:0x00:0x00:0x00:0x01:0x01:0x01 test.jcdk.applet.TestApplet test.jcdk.applet 0xD0:0x00:0x00:0x00:0x01:0x01 1.0
Executing E:\eclipse-oxygen-64bit\JCDKit_305u2\bin/scriptgen.bat -package test.jcdk.applet -o G:\eclipse_javacard\workspace\TestJCDKApplet\apdu_scripts/cap-test.jcdk.applet.script G:\eclipse_javacard\workspace\TestJCDKApplet\deliverables/test/jcdk/applet/javacard/applet.cap
Modified to generate the required script files (listed only the last two, first two scripts do not change):
G:\eclipse_javacard\workspace\TestJCDKApplet>E:\eclipse-oxygen-64bit\JCDKit_305u2\bin\verifycap.bat -outfile applet.hash E:\eclipse-oxygen-64bit\JCDKit_305u2\api_export_files\java\lang\javacard\lang.exp E:\eclipse-oxygen-64bit\JCDKit_305u2\api_export_files\javacard\framework\javacard\framework.exp .\deliverables\test\jcdk\applet\javacard\applet.exp .\deliverables\test\jcdk\applet\javacard\applet.cap
[ INFO: ] Verifier [v3.0.5]
[ INFO: ] Copyright (c) 1998, 2017, Oracle and/or its affiliates. All rights reserved.
[ INFO: ] Verifying CAP file .\deliverables\test\jcdk\applet\javacard\applet.cap
[ INFO: ] Digest for test/jcdk/applet/javacard/Header.cap [SHA-256: 22e589e7bbb45e420c2a17d5b8abcc437c52f00ecfb15b48ed3257f87eff62f9]
[ INFO: ] Digest for test/jcdk/applet/javacard/Directory.cap [SHA-256: bc72a8594664c9720c38afab7c87b7dda894088f53faefcac548463a4186fbe9]
[ INFO: ] Digest for test/jcdk/applet/javacard/Import.cap [SHA-256: e58492b256b4af8d7f1860f18e57c5336e254a618c2518c987dcefb33db0a8d0]
[ INFO: ] Digest for test/jcdk/applet/javacard/ConstantPool.cap [SHA-256: 6c5bf615cd3746d52c815e8264b910a41a94217161862a7520087799fd03098b]
[ INFO: ] Digest for test/jcdk/applet/javacard/StaticField.cap [SHA-256: 1ec76ec50280f5d8822179bb1b268ae7c2383d9fbe4d6c2beb427090dbf53dfd]
[ INFO: ] Digest for test/jcdk/applet/javacard/RefLocation.cap [SHA-256: b2b3f5e23eee662b8c406212d5cb291959a8eeddb92e58b9a45941c0b91388be]
[ INFO: ] Digest for test/jcdk/applet/javacard/Descriptor.cap [SHA-256: 292e4bd46d836b8501a19a9ea92b1ec976eca1b4920bb03499236284d17be2d7]
[ INFO: ] Digest for test/jcdk/applet/javacard/Class.cap [SHA-256: 6c68abd77e3481a00ae2462cfc8f416ae38d4d0e4b02c685145c39d30d132526]
[ INFO: ] Digest for test/jcdk/applet/javacard/Debug.cap [SHA-256: 7341f35fee494363bb8b84e8c132399a33a0bb4d39fd9192e92be680c08019d3]
[ INFO: ] Digest for test/jcdk/applet/javacard/Method.cap [SHA-256: 651231359c6bb65fbcb0e3a49f52cee1a682ed7e97610365b374583638757365]
[ INFO: ] Digest for test/jcdk/applet/javacard/Applet.cap [SHA-256: e1de8850f009796b9b991757dd378353128e10d4bc6400e5bbd970516bf187f1]
[ INFO: ] Verification completed with 0 warnings and 0 errors.
(Note: you have to add the path to the jcdk export files used by the applet, these you can find out by activating verbose output in the java card package settings and searching the console output for referenced exp files.)
Then at lease you can generate the install script with the command:
G:\eclipse_javacard\workspace\TestJCDKApplet>E:\eclipse-oxygen-64bit\JCDKit_305u2\bin/scriptgen.bat -package test.jcdk.applet -o
G:\eclipse_javacard\workspace\TestJCDKApplet\apdu_scripts/cap-test.jcdk.applet.script G:\eclipse_javacard\workspace\TestJCDKApplet\deliverables/test/jcdk/applet/javacard/applet.cap -hashfile applet.hash
ScriptGen [v3.0.5]
Copyright (c) 1998, 2017, Oracle and/or its affiliates. All rights reserved.
APDU script file for CAP file download generated.