From: Sebastian Schuberth <sschuberth@gmail.com>
To: bitbake-devel@lists.openembedded.org
Subject: Generating SPDX documents without actually building
Date: Thu, 2 May 2024 18:01:27 +0200 [thread overview]
Message-ID: <CAHGBnuOn-i=R0cxfWqGgQUsDnKjcrP3ERhX1jnZhgVRsWz=fhg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
Hi all,
to start with a disclaimer, I'm a total noob when it comes to Open Embedded
/ Embedded Linux / Yocto / BitBake stuff. That said, I'm in need of
creating SPDX documents for Yocto projects in the context of [1]. I'm
already quite far in that I work with Poky and programmatically run
something like
bitbake -r
/home/sebastian/Development/GitHub/doubleopen-project/ort/plugins/package-managers/bitbake/src/main/resources/spdx.conf
-c create_spdx xmlto
However, I continuously run into various build problems on my Fedora 40
machine (one of which has been recently addressed by [2]), let alone the
time it takes to build something from scratch, even something as small as
e.g. the "xmlto" target. So, ideally, I would be able to create SPDX
documents without really building any binaries at all. I probably want all
the source download and patching to happen, in order to archive the patched
code that goes into the binaries, but skip the actual compiler / linker
invocations to save time, and just create the SPDX documents.
Is something like this already possible somehow, maybe by setting from
compiler / linker variables to fake scripts that just do nothing?
Thanks for any insights!
[1]: https://github.com/oss-review-toolkit/ort/issues/722
[2]:
https://github.com/openembedded/bitbake/commit/f10e630fd7561746d835a4378e8777e78f56e44a
--
Sebastian Schuberth
[-- Attachment #2: Type: text/html, Size: 3203 bytes --]
next reply other threads:[~2024-05-02 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 16:01 Sebastian Schuberth [this message]
2024-05-08 10:19 ` Generating SPDX documents without actually building Sebastian Schuberth
2024-05-08 10:24 ` [bitbake-devel] " Alexander Kanavin
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='CAHGBnuOn-i=R0cxfWqGgQUsDnKjcrP3ERhX1jnZhgVRsWz=fhg@mail.gmail.com' \
--to=sschuberth@gmail.com \
--cc=bitbake-devel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).