Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "hongxu" <hongxu.jia@eng.windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 1/2] cdrtools-native: fix booting EFI ISO live failed
Date: Mon, 28 Apr 2025 09:55:08 -0700	[thread overview]
Message-ID: <25979.1745859308517888166@lists.openembedded.org> (raw)
In-Reply-To: <AE38D3E5-5632-4C2C-ABBD-D213983EBD63@arm.com>

[-- Attachment #1: Type: text/plain, Size: 928 bytes --]

Hi Alex,

I will update to Inactive-Upstream. in v3

About schilytools, it could not be built from cdrtools recipe directly,  the reason is schilytools using a bootstrap 'smake' binary for compiling
which is created in the psmake/ directory from source [1].  We need to create the recipe schilytools from scratch.

Due to cdrtools have license problem[2], we only have cdrtools-native support in Yocto. For schilytools - the fork of cdrtools, I think we should only support schilytools-native also

[1] https://codeberg.org/schilytools/schilytools/commit/a72089c47380426830118d318d59a65e9e1b2aff
[2] https://lwn.net/Articles/195167/

Hi Ross,

For libisoburn[3], it is not alive since 2023

[3] https://files.libburnia-project.org/

Hi RP,

What is your suggestions, is it necessary to use schilytools or libisoburn to instead of cdrtools in oe-core. It beyond the scope of this bug fix patch

//Hongxu

[-- Attachment #2: Type: text/html, Size: 2205 bytes --]

  reply	other threads:[~2025-04-28 16:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-26  8:03 [PATCH v2 1/2] cdrtools-native: fix booting EFI ISO live failed Hongxu Jia
2025-04-26  8:03 ` [PATCH v2 2/2] syslinux: improve isohybrid to process extra sector count for ISO 9660 image Hongxu Jia
2025-04-28  9:31 ` [OE-core] [PATCH v2 1/2] cdrtools-native: fix booting EFI ISO live failed Alexander Kanavin
2025-04-28 10:56   ` Ross Burton
2025-04-28 16:55     ` hongxu [this message]
2025-04-28 18:18       ` Alexander Kanavin
2025-04-29  3:59         ` hongxu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25979.1745859308517888166@lists.openembedded.org \
    --to=hongxu.jia@eng.windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox