Unable to build for tizen

[wrgallo]

Bug description

The tutorial on building from source is very simple:

1. Clone repository
2. Run npm install
3. Run

   # All three variants in one command
   npm run build:tizen:all
   
   # Or individually
   npm run build:tizen         # Regular
   npm run build:tizen:oblong  # Oblong (512x423 launcher icon)
   npm run build:tizen:legacy  # Legacy (Tizen 2.4, no Smart Hub Preview)
   

However this is failing with:

[build] Cleaning up old output...
[build] Verifying Samsung certificate...
[!] Samsung certificate files not found at: C:\Users\wrgal\SamsungCertificate\Moonfin
[!] Expected: author.p12 and distributor.p12
[!] Please create a Samsung certificate via Tizen Studio Certificate Manager.
[!] Falling back to unsigned build...
[!] Tizen profiles.xml not found at: C:\Users\wrgal\tizen-studio-data\profile\profiles.xml
[build] Packaging unsigned .wgt with profile "Moonfin"...
[build] Running: "tizen" package -t wgt -- "C:\Users\wrgal\Documents\github\moonfin\packages\build-tizen\dist" -o "C:\Users\wrgal\Documents\github\moonfin"
Arquivo não encontrado
O sistema não pode encontrar o arquivo C:\Users\wrgal\Documents\github\moonfin\packages\build-tizen\\..\..\..\sdk.info.
Erro: Não foi possível localizar nem carregar a classe principal org.tizen.ncli.ide.shell.Main
Causada por: java.lang.ClassNotFoundException: org.tizen.ncli.ide.shell.Main

This feels like a bug, however bug reports are only allowed for playback/seer/UI.

Not only it tried to find an invalid path, but the string for this path is not even a valid path string. I mean look at the part: build-tizen\\..\

Information

• The repository was cloned into the folder: C:\Users\wrgal\Documents\github\moonfin
• I have Tizen Studio installed, and have been using to compile jellyfin-web. The sdk.info in my case is available at C:\tizen-studio\sdk\sdk.info
• If it matters I use it to compile to the TV model: QN65Q80TAGXZD, which has Platform version: Tizen 5.5

[RadicalMuffinMan]

Hi! Thanks for the write up, this is a real bug and a good catch.

Here's what's going on. The build script checks a handful of known spots for Tizen tooling, and yours sits one level deeper than any of them (C:\tizen-studio\sdk..., which lines up with your sdk.info being at C:\tizen-studio\sdk\sdk.info). When it didn't find it, it fell back to just running tizen and letting Windows sort it out from PATH.

That's where the weird path comes from. The Tizen launcher figures out where it lives based on the path it was called with, then goes looking for sdk.info a few folders up. Called by bare name, it measures from your current directory instead, which was packages\build-tizen inside your clone. So it went hunting for its own Java libraries in the Moonfin source tree, came up empty, and died with the ClassNotFoundException. That doubled backslash is Tizen's own string joining, not ours.

The certificate and profiles.xml warnings were unrelated and harmless, though those paths were wrong for Windows anyway.

Fixed on main:

• The CLI always gets called by full path now, and more install layouts are recognised, yours included. There's a TIZEN_CLI variable too if an install ever ends up somewhere odd.
• If the CLI is there but can't start, you get told up front instead of a Java stack trace later on.
• Packaging doesn't need the zip command anymore, which Windows doesn't have. It's all done in Node now.
• The CLI is genuinely optional, like the wiki always claimed. You only need it if you want to sign the package yourself or push straight to the TV over sdb.

Pull latest and npm run build:tizen:all should just work. If something still trips it up, npm run build:tizen -- --skip-tizen-cli skips the Tizen tooling entirely.

One broader thing worth knowing: Samsung has killed off Tizen Studio completely. The download page just bounces you to https://samsungtizenos.com/ and the VS Code extension now, which ships the same CLI and certificate manager. The build script picks up either one, so your existing install is fine, but new contributors can't even get Studio anymore. So the no-tooling path is really the default going forward, and it's already what we ship. The unsigned .wgt you get out of this is the same package that's on the Releases page, and Apps2Samsung does the signing and installing for you. For a normal sideload onto your Q80T you don't need Samsung tooling or a certificate at all.

Wiki's been updated with all of this, including a troubleshooting entry for this exact error.

[wrgallo]

Building

Now it builds thank you very much.

Signing the widget

Regarding TIZEN_PROFILES_XML, it seems it does NOT look the path for author.p12 and distributor.p12 from the file profiles.xml, and expects them to be on the same folder.

Running:

set SDB=C:\tizen-studio\sdk\tools\sdb

Rem Signing profile name (default Moonfin)
set TIZEN_SIGN_PROFILE=Sample3

Rem Full path to your tooling's profiles.xml
set TIZEN_PROFILES_XML=C:\tizen-studio\data\profile\profiles.xml

Rem Full path to tizen / tizen.bat
set TIZEN_CLI=C:\tizen-studio\sdk\tools\ide\bin\tizen

npm install
run build:tizen

Where profiles.xml is:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<profiles active="Sample3" version="3.1">
<profile name="Sample2">
<profileitem ca="" distributor="0" key="C:\Users\wrgal\SamsungCertificate\Sample2\author.p12" password="C:\Users\wrgal\SamsungCertificate\Sample2\author.pwd" rootca=""/>
<profileitem ca="" distributor="1" key="C:\Users\wrgal\SamsungCertificate\Sample2\distributor.p12" password="C:\Users\wrgal\SamsungCertificate\Sample2\distributor.pwd" rootca=""/>
<profileitem ca="" distributor="2" key="" password="" rootca=""/>
</profile>
<profile name="DummyCertificate">
<profileitem ca="C:\tizen-studio\sdk\tools\certificate-generator\certificates\developer\tizen-developer-ca.cer" distributor="0" key="C:\Users\wrgal\SamsungCertificate\Sample\author.p12" password="C:\Users\wrgal\SamsungCertificate\Sample\author.pwd" rootca=""/>
<profileitem ca="C:\tizen-studio\sdk\tools\certificate-generator\certificates\distributor\tizen-distributor-ca-new.cer" distributor="1" key="C:\tizen-studio\sdk\tools\certificate-generator\certificates\distributor\tizen-distributor-signer-new.p12" password="C:\tizen-studio\data\tools\certificate-generator\certificates\distributor\tizen-distributor-signer-new.pwd" rootca=""/>
<profileitem ca="" distributor="2" key="" password="" rootca=""/>
</profile>
<profile name="Sample3">
<profileitem ca="" distributor="0" key="C:\Users\wrgal\Documents\github\jellyfin\tyzen_certificate_backup_path\author.p12" password="C:\Users\wrgal\Documents\github\jellyfin\tyzen_certificate_backup_path\author.pwd" rootca=""/>
<profileitem ca="" distributor="1" key="C:\Users\wrgal\SamsungCertificate\Sample3\distributor.p12" password="C:\Users\wrgal\SamsungCertificate\Sample3\distributor.pwd" rootca=""/>
<profileitem ca="" distributor="2" key="" password="" rootca=""/>
</profile>
</profiles>

Still results in unsigned widget:

[✓] Pruned ilib locale data
[build] Cleaning up old output...
[build] Removed Moonfin_Tizen_Regular_2.6.0.wgt
[build] Verifying Samsung certificate...
[!] Samsung certificate files not found at: C:\Users\wrgal\SamsungCertificate\Sample3
[!] Expected: author.p12 and distributor.p12
[!] Create them with the certificate manager in your Tizen tooling,
[!] or set TIZEN_CERT_DIR to the folder that already holds them.
[✓] Signing profile "Sample3" found in profiles.xml
[!] Falling back to unsigned build...
[build] Packaging unsigned .wgt...
[✓] Package created: C:\Users\wrgal\Documents\github\moonfin\Moonfin_Tizen_Regular_2.6.0.wgt (4.09 MB)

══════════════════════════════════════════════════
  Build Complete! (v2.6.0)
══════════════════════════════════════════════════

  Output: C:\Users\wrgal\Documents\github\moonfin\Moonfin_Tizen_Regular_2.6.0.wgt