From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: yocto@lists.yoctoproject.org, sschuberth@gmail.com
Subject: Re: [yocto] Generating SPDX documents without actually building anything
Date: Wed, 08 May 2024 13:53:18 +0100 [thread overview]
Message-ID: <349c2caef16b0f7428864a6ce56328caadd4bff9.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAHGBnuPBiOEEHnnCuPA-1AxTq60qCsMcP3-y=PvkVqguGyAt+w@mail.gmail.com>
On Wed, 2024-05-08 at 13:59 +0200, Sebastian Schuberth via
lists.yoctoproject.org wrote:
> 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?
The SPDX generated information includes information about the generated
binaries, the dependencies between them and also traces license headers
used by a given binary through the binary debug information.
Whilst it is true you could generate a simpler SPDX document without
compiling anything, that isn't how our SPDX generation currently works,
it includes a lot more information and some of that is from the
binaries.
You could create a different simpler spdx like class that could do what
you describe but that isn't what we have today. We went for the version
with all the information.
Cheers,
Richard
prev parent reply other threads:[~2024-05-08 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 11:59 Generating SPDX documents without actually building anything Sebastian Schuberth
2024-05-08 12:13 ` [yocto] " Alexander Kanavin
2024-05-08 12:53 ` Richard Purdie [this message]
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=349c2caef16b0f7428864a6ce56328caadd4bff9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=sschuberth@gmail.com \
--cc=yocto@lists.yoctoproject.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).